Is there a way to query nimbus to find out what the current isolation scheduler configuration is? It'd be nice to have that incorporated into my topology deployment. If this is a bad pattern, can someone recommend a simple way to be at least marginally less static than updating the isolation scheduler config on nimbus and hardcoding your topology to match?
- isolation scheduler state Luke Rohde
- Re: isolation scheduler state Nathan Marz
