cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Motta (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-14084) Disks can be imbalanced during replace of same address when using JBOD
Date Thu, 30 Nov 2017 17:19:00 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-14084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Paulo Motta updated CASSANDRA-14084:
------------------------------------
    Status: Patch Available  (was: In Progress)

> 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
>
> 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message