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

split/main/join should be able to take different cluster templates #3

Open
wheaton5 opened this issue Jan 11, 2018 · 4 comments
Open

Comments

@wheaton5
Copy link

Sometimes a join method runs very long and requires a different queue or you want the split to run locally.

@adam-azarchs
Copy link
Member

adam-azarchs commented Jan 11, 2018

Interesting idea. We had been toying with the idea of allowing the split to run locally, particularly in the cases where the split is trivial. We provisionally decided against it because of the risk that a "trivial" split could grow to become non-trivial and tie up serious resources on the submit host.

As for different queues, there is the concept of the __special resource which gets inserted into the __MRO_JOBRESOURCES__ template variable (see https://github.com/martian-lang/martian/blob/master/src/martian/core/jobmanager.go#L569). Granted it's very poorly documented how to use that, but at least for chunks and joins, the split phase could use that to specify a special queue. Does that satisfy your use case?

@wheaton5
Copy link
Author

As I don't have access to 10XDev, I cannot view the url you sent. It does sound like it covers my main use case which is on a cluster that has a queue that limits me to 12 hours on the normal queue and some join phases possibly taking longer.

@adam-azarchs
Copy link
Member

Sorry about that, fixed the link.

@adam-azarchs
Copy link
Member

One note on that feature is there's a bug in martian 2.3 which may prevent that from working correctly. It's fixed in 2.3.1.

nlhepler pushed a commit that referenced this issue Oct 26, 2018
Teach rust adapter to work with new monitor parent
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants