Details
-
Improvement
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
None
-
None
Description
We currently invalidate disk boundaries whenever instantiating a new replication strategy, but this is done whenever updating keyspace settings.
Computing new boundaries is expensive and unnecessarily invalidating them will cause DiskBoundaries consumers to also invalidate their work unnecessarily. For instance, after CASSANDRA-13948 the CompactionStrategyManager will reload all compaction strategies when the boundaries are invalidated.
In this case, we should only invalidate the disk boundaries when the replication settings change to avoid doing unnecessary work.
Attachments
Attachments
Issue Links
- is related to
-
CASSANDRA-13948 Reload compaction strategies when JBOD disk boundary changes
- Resolved
-
CASSANDRA-14084 Disks can be imbalanced during replace of same address when using JBOD
- Resolved