[ https://issues.apache.org/jira/browse/CASSANDRA-14084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16274400#comment-16274400 ]
Paulo Motta commented on CASSANDRA-14084: ----------------------------------------- testall is clean, dtest failures [seem unrelated|https://issues.apache.org/jira/secure/attachment/12900219/dtest14084.png] > Disks can be imbalanced during replace of same address when using JBOD > ---------------------------------------------------------------------- > > Key: CASSANDRA-14084 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14084 > Project: Cassandra > Issue Type: Bug > Reporter: Paulo Motta > Assignee: Paulo Motta > Attachments: dtest14084.png > > > While investigating CASSANDRA-14083, I noticed that [we use the pending > ranges to calculate the disk > boundaries|https://github.com/apache/cassandra/blob/41904684bb5509595d11f008d0851c7ce625e020/src/java/org/apache/cassandra/db/DiskBoundaryManager.java#L91] > 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|https://github.com/apache/cassandra/blob/41904684bb5509595d11f008d0851c7ce625e020/src/java/org/apache/cassandra/service/StorageService.java#L1449] > (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. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org