New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[elan] Deploy Elan VM before April downtime #41
Comments
RP has provisioned a machine to use during the downtime period. I'll work on packaging Elan up a bit better to deploy it there before next Thursday. |
Will also need to sort out |
Committed to production -- tomorrow's Elan run should use the new node |
Absolutely. Blazing.
🔥 |
RP says the connection to Majora will be a little slower from this node, but we're able to blow twice as many Ocarinas at the post-Elan step. Publishing and MQTT still to come. |
Forgot that part of the post-Elan publish step is sent to SLURM but have parameterised the publish mode and committed that change to Elan (SamStudio8/elan-nextflow@c4f9dcc). After a little conda faff (is it bioinformatics without it?) everything finished up in record time, and emitted a message to MQTT without trouble. Will keep an eye out tomorrow morning but I'm happy. |
Encountered an issue early this morning caused by Nextflow exceeding the thread pool limit when resuming tasks with the local executor. This has been reported before (nextflow-io/nextflow#1871) and the proposed fix to add |
Additionally, the Error below for posterity;
Update: This error has gone away now. We might want to lower |
No description provided.
The text was updated successfully, but these errors were encountered: