Details
-
Bug
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
None
-
None
-
Normal
Description
While investigating CASSANDRA-14083, I noticed that we use the pending ranges to calculate the disk boundaries when the node is bootstrapping.
The problem is that when the node is replacing a node with the same address, it sets itself as normal locally (for other unrelated reasons), so the local ranges will be null and consequently the disk boundaries will be null. This will cause the sstables to be randomly spread across disks potentially causing imbalance.
Attachments
Attachments
Issue Links
- relates to
-
CASSANDRA-12344 Forward writes to replacement node with same address during replace
- Open
-
CASSANDRA-14083 Avoid invalidating disk boundaries unnecessarily
- Resolved