-
Notifications
You must be signed in to change notification settings - Fork 6
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
MANTA-4932 rebalancer should not start jobs if snaplinks are enabled #59
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still wrapping my head around the entirety of this change. Looks pretty good. I had some questions mostly. Also, if I'm understanding it correctly, it looks like most of this is really about being able to reload config information in a running process whenever changes are received. The actual code to address MANTA-4932 is relatively small. Is that right?
1dbae13
to
4243943
Compare
|
||
trace!("Got picker response: {:#?}", response); | ||
|
||
// Storinfo, or our connection to it, is sick. So instead of | ||
// breaking out of the loop and possibly returning partial results we | ||
// return an empty Vec. | ||
if response.status() != StatusCode::OK { | ||
error!("Could not contact storinfo service {:#?}", response); | ||
return vec![]; | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the part that was added for "MANTA-4961 rebalancer job should not start if storinfo is unavailable"
I still have some testing to do but I wanted to get this posted so people can start to familiarize themselves with the change.