planb-cassandra
planb-cassandra copied to clipboard
Interactive update command improvements
We would like to make the update command behavior less surprising by implementing the following improvements:
- [ ] document how to resolve 'failed' state, maybe provide a hint as well
- [ ] assess the current state of the node and allow to skip updating if it already matches the target configuration
- [x] unattended mode: fire and forget (should still stop if some nodes go down unexpectedly)
- [x] better node liveliness probe (DownEndpointCount is not a good fit)
If the original node has detailed monitoring enabled it will be gone in the new node
@lmineiro didn't know about that. We should probably have it as an option for create and update.
skip updating if it already matches the target configuration
In common cases like updating the AMI, this can be addressed by using filters. That is filter for nodes running the old AMI. This makes it easier to continue if update broke in the middle.