Skip to content

📝 add hints on troubleshooting running jobs#21

Open
enryH wants to merge 5 commits intomainfrom
seqera_azure
Open

📝 add hints on troubleshooting running jobs#21
enryH wants to merge 5 commits intomainfrom
seqera_azure

Conversation

@enryH
Copy link
Copy Markdown
Collaborator

@enryH enryH commented Nov 12, 2025

See the preview for the last modified PR:

@enryH enryH requested review from apalleja and Copilot April 1, 2026 10:37
@enryH enryH marked this pull request as ready for review April 1, 2026 10:38
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds additional guidance to the Seqera/Azure Batch infrastructure notes, focusing on node allocation behavior and troubleshooting pipeline launch issues from Seqera Platform.

Changes:

  • Document Azure Batch “spreading vs packing” behavior with a reference link.
  • Add troubleshooting notes for connection issues (with screenshots) and guidance on handling mixed VM size requirements via autopools.
  • Add a new screenshot asset for the Compute Environment configuration UI.

Reviewed changes

Copilot reviewed 1 out of 3 changed files in this pull request and generated 4 comments.

File Description
seqera/setup_infrastructure.md Adds new operational notes (node packing/spreading) and a troubleshooting section (timeouts, screenshots, VM sizing/autopool pointers).
seqera/assets/seqera_compute_env_0.png Adds a screenshot referenced by the new troubleshooting section.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +49 to +55
If you encounter connection issues when launching pipelines from Seqera using
Azure Batch compute environment, try to increase the timeout settings in the
Compute Environment configuration on Seqera Platform to around 8-16 hours.

```
NXF_OPTS="-Dsun.net.client.defaultConnectTimeout=30000 -Dsun.net.client.defaultReadTimeout=60000"
```
Copy link

Copilot AI Apr 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The text says to increase timeouts to ~8–16 hours, but the shown NXF_OPTS values (30000/60000) are only 30s/60s (and are typically interpreted as milliseconds). Please align the stated duration with the actual values and/or explicitly state the units.

Copilot uses AI. Check for mistakes.
Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

to figure out

Comment on lines +53 to +67
```
NXF_OPTS="-Dsun.net.client.defaultConnectTimeout=30000 -Dsun.net.client.defaultReadTimeout=60000"
```

Here are some example screenshots for setting it as global Environment variables

![Timeout settings in Compute Environment](assets/seqera_compute_env_0.png)
![Timeout settings in Compute Environment](assets/seqera_compute_env_1.png)

So you will need to set the `NXF_OPTS` environment variable in the Compute Environment
configuration on Seqera Platform to

```
-Dsun.net.client.defaultConnectTimeout=30000 -Dsun.net.client.defaultReadTimeout=60000
```
Copy link

Copilot AI Apr 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The two code blocks for NXF_OPTS are inconsistent (one includes NXF_OPTS="...", the other only the JVM args). Please clarify what exactly should be entered in the Seqera UI field(s) and keep a single, unambiguous example.

Copilot uses AI. Check for mistakes.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants