[jira] [Updated] (CASSANDRA-9363) Expose vnode to directory assignment
[ https://issues.apache.org/jira/browse/CASSANDRA-9363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-9363: --- Fix Version/s: (was: 3.x) > Expose vnode to directory assignment > > > Key: CASSANDRA-9363 > URL: https://issues.apache.org/jira/browse/CASSANDRA-9363 > Project: Cassandra > Issue Type: Improvement >Reporter: Nick Bailey >Assignee: Marcus Eriksson > > CASSANDRA-6696 adds the feature of pinning vnodes to specific disks to > improve things when JBOD is being used. > We also need a way to introspect what vnodes are assigned where. I'm not sure > what the easiest/best way to expose that info is. JMX/manifest file/system > table could all be a valid option. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-9363) Expose vnode to directory assignment
[ https://issues.apache.org/jira/browse/CASSANDRA-9363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-9363: -- Assignee: Marcus Eriksson > Expose vnode to directory assignment > > > Key: CASSANDRA-9363 > URL: https://issues.apache.org/jira/browse/CASSANDRA-9363 > Project: Cassandra > Issue Type: Improvement >Reporter: Nick Bailey >Assignee: Marcus Eriksson > Fix For: 3.x > > > CASSANDRA-6696 adds the feature of pinning vnodes to specific disks to > improve things when JBOD is being used. > We also need a way to introspect what vnodes are assigned where. I'm not sure > what the easiest/best way to expose that info is. JMX/manifest file/system > table could all be a valid option. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
