[jira] [Updated] (CASSANDRA-10486) Expose tokens of bootstrapping nodes in JMX
[ https://issues.apache.org/jira/browse/CASSANDRA-10486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-10486: -- Issue Type: Improvement (was: Bug) > Expose tokens of bootstrapping nodes in JMX > --- > > Key: CASSANDRA-10486 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10486 > Project: Cassandra > Issue Type: Improvement > Components: Observability >Reporter: Nick Bailey >Priority: Minor > Fix For: 2.2.x > > > Currently you can get a list of bootstrapping nodes from JMX, but the only > way to get the tokens of those bootstrapping nodes is to string parse info > from the failure detector. This is fragile and can easily break when changes > like https://issues.apache.org/jira/browse/CASSANDRA-10330 happen. > We should have a clean way of knowing the tokens of bootstrapping nodes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-10486) Expose tokens of bootstrapping nodes in JMX
[ https://issues.apache.org/jira/browse/CASSANDRA-10486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-10486: -- Component/s: Observability > Expose tokens of bootstrapping nodes in JMX > --- > > Key: CASSANDRA-10486 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10486 > Project: Cassandra > Issue Type: Improvement > Components: Observability >Reporter: Nick Bailey >Priority: Minor > Fix For: 2.2.x > > > Currently you can get a list of bootstrapping nodes from JMX, but the only > way to get the tokens of those bootstrapping nodes is to string parse info > from the failure detector. This is fragile and can easily break when changes > like https://issues.apache.org/jira/browse/CASSANDRA-10330 happen. > We should have a clean way of knowing the tokens of bootstrapping nodes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-10486) Expose tokens of bootstrapping nodes in JMX
[ https://issues.apache.org/jira/browse/CASSANDRA-10486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne updated CASSANDRA-10486: - Assignee: (was: Stefania) > Expose tokens of bootstrapping nodes in JMX > --- > > Key: CASSANDRA-10486 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10486 > Project: Cassandra > Issue Type: Bug >Reporter: Nick Bailey >Priority: Minor > Fix For: 2.2.x > > > Currently you can get a list of bootstrapping nodes from JMX, but the only > way to get the tokens of those bootstrapping nodes is to string parse info > from the failure detector. This is fragile and can easily break when changes > like https://issues.apache.org/jira/browse/CASSANDRA-10330 happen. > We should have a clean way of knowing the tokens of bootstrapping nodes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-10486) Expose tokens of bootstrapping nodes in JMX
[ https://issues.apache.org/jira/browse/CASSANDRA-10486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne updated CASSANDRA-10486: - Fix Version/s: 2.2.x > Expose tokens of bootstrapping nodes in JMX > --- > > Key: CASSANDRA-10486 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10486 > Project: Cassandra > Issue Type: Bug >Reporter: Nick Bailey >Assignee: Stefania >Priority: Minor > Fix For: 2.2.x > > > Currently you can get a list of bootstrapping nodes from JMX, but the only > way to get the tokens of those bootstrapping nodes is to string parse info > from the failure detector. This is fragile and can easily break when changes > like https://issues.apache.org/jira/browse/CASSANDRA-10330 happen. > We should have a clean way of knowing the tokens of bootstrapping nodes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-10486) Expose tokens of bootstrapping nodes in JMX
[ https://issues.apache.org/jira/browse/CASSANDRA-10486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Bailey updated CASSANDRA-10486: Assignee: Brandon Williams > Expose tokens of bootstrapping nodes in JMX > --- > > Key: CASSANDRA-10486 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10486 > Project: Cassandra > Issue Type: Bug >Reporter: Nick Bailey >Assignee: Brandon Williams >Priority: Minor > > Currently you can get a list of bootstrapping nodes from JMX, but the only > way to get the tokens of those bootstrapping nodes is to string parse info > from the failure detector. This is fragile and can easily break when changes > like https://issues.apache.org/jira/browse/CASSANDRA-10330 happen. > We should have a clean way of knowing the tokens of bootstrapping nodes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-10486) Expose tokens of bootstrapping nodes in JMX
[ https://issues.apache.org/jira/browse/CASSANDRA-10486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-10486: - Reviewer: Brandon Williams We should probably expose a map of endpoint states in Gossiper and convert anything that's not a simple type like ApplicationState to something that is. We could later use that in nodetool instead of having the FD construct the string for us. > Expose tokens of bootstrapping nodes in JMX > --- > > Key: CASSANDRA-10486 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10486 > Project: Cassandra > Issue Type: Bug >Reporter: Nick Bailey >Assignee: Stefania >Priority: Minor > > Currently you can get a list of bootstrapping nodes from JMX, but the only > way to get the tokens of those bootstrapping nodes is to string parse info > from the failure detector. This is fragile and can easily break when changes > like https://issues.apache.org/jira/browse/CASSANDRA-10330 happen. > We should have a clean way of knowing the tokens of bootstrapping nodes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
