Details
-
Task
-
Status: Open
-
Low
-
Resolution: Unresolved
-
None
-
None
Description
Feels like this "mostly works" but is generally fragile (see: shuffle).
Would be good to get a fresh perspective on it and see if we can do better.
Bonus would be, ability to bootstrap multiple nodes w/o Two Minute Rule. Probably would involve using LWT on pending ranges state.
Attachments
Issue Links
- relates to
-
CASSANDRA-14660 Improve TokenMetaData cache populating performance for large cluster
- Resolved