Details
-
New Feature
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
M5
Description
This tracks work required to handle a few similar use cases:
- node crashes and doesn't come back ever. a new node needs to be recruited to get a tablet's replication back up to 3
- equivalently, a node loses its disks and thus is essentially a new node
- add a new node to the cluster, and balance some existing data onto that one
Implementation-wise:
- ability to bootstrap a new node into a quorum (copy existing tablet data)
- ability to change-config a quorum to include a new peer
- some administrative commands to explicitly migrate data to perform manual load balancing (automatic load balancing tracked separately)
Attachments
Issue Links
- blocks
-
KUDU-673 Automatic Master management of dynamic consensus configuration
- Resolved