Production checklist v1 #691
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for seqera-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Signed-off-by: Justine Geffen <[email protected]>
Signed-off-by: Justine Geffen <[email protected]>
Signed-off-by: Justine Geffen <[email protected]>
Signed-off-by: Justine Geffen <[email protected]>
justinegeffen
added
1. Editor review
|
@gavinelder, would really appreciate your input on the infra section. The goal is to keep iterating on this document and this is v1. |
Stylistic and language changes Signed-off-by: Justine Geffen <[email protected]>
Signed-off-by: Justine Geffen <[email protected]>
Signed-off-by: Justine Geffen <[email protected]>
|
|
||
| Infrastructural requirements differ widely based on the workload you’re expecting. | ||
|
|
||
| To begin with, build out a proof of concept using the below recommendations, to create a baseline of your capacity requirements. Once you’re ready to move to production, take into account the increased workload you’d expect. Here are some starting points for estimating compute and database requirements. |
There was a problem hiding this comment.
Do we have any examples we can provide as a good template for getting started?
|
|
||
| These autoscale for pipeline runs, but the sizing recommendation will be based on the workload and can vary significantly based on the number of pipelines, and number of concurrent processes, you have in mind. Consult the [Azure autoscaling documentation](https://learn.microsoft.com/en-us/azure/azure-monitor/autoscale/autoscale-get-started) for information about scaling in Azure. | ||
|
|
||
| ## Spot instance retry strategy |
There was a problem hiding this comment.
Would we provide an example here or link to one?
There was a problem hiding this comment.
The tutorial we link to does cover the retry strategy but you make a good point. Maybe this would be better as a list with links to sections within the tutorial.
|
|
||
| ## Seqera Platform limitations | ||
|
|
||
| When cancelling large runs, make sure to check that all jobs were killed in your compute environment (ZOMBIE JOBS). Large runs sometimes leak jobs because Nextflow is killed before it can cancel all of them, which can lead to significant cost overruns. |
There was a problem hiding this comment.
How can I do this as a user? How do I know what a zombie job is?
justinegeffen
commented
Jul 16, 2025
Signed-off-by: Justine Geffen <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WIP first draft of production checklist to cover infrastructure, retry strategy, security, and Platform limitations.
Outstanding
@netlify /platform-cloud/getting-started/production-checklist