Skip to content
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

Tool burst submission fails on 16.01 release #2259

Closed
Takadonet opened this issue Apr 27, 2016 · 5 comments
Closed

Tool burst submission fails on 16.01 release #2259

Takadonet opened this issue Apr 27, 2016 · 5 comments

Comments

@Takadonet
Copy link
Contributor

Attempted to use tool burst submission parameters from galaxy.ini on a multiple paralleled workflow. First stage worked correctly but got the following stacktrace when attempting stage two.

https://gist.github.com/Takadonet/080ca51143cefee4a15268b54598b749

commit : b794740

galaxy.ini
tool_submission_burst_threads = 4
tool_submission_burst_at = 30

Using supervisord for headless handlers.

@dannon
Copy link
Member

dannon commented May 3, 2016

Hopefully resolved with #2260

Please let us know if you still see this after that change.

@dannon dannon closed this as completed May 3, 2016
@jmchilton
Copy link
Member

I think he said it still isn't working - but sounds like we made some progress. I'm looking into the next problem now - I'll see if I can reproduce locally.

@dannon
Copy link
Member

dannon commented May 3, 2016

Yeah, reopening this, because I'm pretty sure the change in #2260 won't fix the problem above.

@dannon dannon reopened this May 3, 2016
@Takadonet
Copy link
Contributor Author

#2260 patch does fix the issue but still was not able to successfully run a full workflow. What is happening now is that downstream tools are not waiting for their inputs to be 'ok' state but simple starting right after being created. In my case, freebayes and mpileup jobs will immediate run even before their smalt map job is done. http://imgur.com/tgkbj6n

@mvdbeek
Copy link
Member

mvdbeek commented Aug 4, 2020

We've removed the broken burst scheduling quite some time ago, closing this then.

@mvdbeek mvdbeek closed this as completed Aug 4, 2020
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

No branches or pull requests

4 participants