[
https://issues.apache.org/jira/browse/KUDU-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon resolved KUDU-434.
------------------------------
Resolution: Fixed
Fix Version/s: n/a
I think this umbrella ticket has outlived its useful life, since the main work
has been integrated for nigh on a year and we've been filing new bugs/work
against the same area as separate JIRAs. Doesn't make sense to have it keep
hanging around as a blocker. We can upgrade individual subtasks or new JIRAs to
blocker status as necessary.
> Add/replace nodes in a tablet (handle permanent node failures) - ability to
> perform manual changes
> --------------------------------------------------------------------------------------------------
>
> Key: KUDU-434
> URL: https://issues.apache.org/jira/browse/KUDU-434
> Project: Kudu
> Issue Type: New Feature
> Components: consensus, tserver
> Affects Versions: M5
> Reporter: Todd Lipcon
> Assignee: Mike Percy
> Priority: Blocker
> Labels: kudu-roadmap
> Fix For: n/a
>
>
> 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)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
