Closed jeffutter closed 4 years ago
Note that PR #15 solves this problem. in addition, there are scenarios where the start order of applications on slave nodes has to be controlled to avoid errors.
@pmenhart oh yeah! Didn’t see that, that would totally cover my use case and is probably more flexible and even has tests 😝.
Hopefully that can get merged and we can close this one.
Yes, I'm going to close this in favour of #15 - which I am intending to merge in some form once I get some clarification on another thread. Thanks for the PR though!
This fixes an issue (specifically with propcheck) where the other nodes would fail to boot. Propcheck tries to access it's context dets file at boot and having multiple instances launch at the same time causes errors like:
The solution for this is to allow local cluster to skip loading certain dependencies when booting the other nodes.