[jira] [Updated] (CASSANDRA-19491) decommissioned nodes show as UNREACHABLE in describecluster afterward
[ https://issues.apache.org/jira/browse/CASSANDRA-19491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-19491: - Resolution: Invalid Status: Resolved (was: Open) I think this is normal until a state is evicted, since this happens on 3.0/3.11 too. > decommissioned nodes show as UNREACHABLE in describecluster afterward > - > > Key: CASSANDRA-19491 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19491 > Project: Cassandra > Issue Type: Bug > Components: Cluster/Membership >Reporter: Brandon Williams >Priority: Normal > Fix For: 4.0.x, 4.1.x, 5.0.x > > > [~urandom] noticed this happening in his cluster and I have been able to > reproduce with a modified dtest. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19491) decommissioned nodes show as UNREACHABLE in describecluster afterward
[ https://issues.apache.org/jira/browse/CASSANDRA-19491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-19491: - Fix Version/s: 4.0.x > decommissioned nodes show as UNREACHABLE in describecluster afterward > - > > Key: CASSANDRA-19491 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19491 > Project: Cassandra > Issue Type: Bug > Components: Cluster/Membership >Reporter: Brandon Williams >Priority: Normal > Fix For: 4.0.x, 4.1.x, 5.0.x > > > [~urandom] noticed this happening in his cluster and I have been able to > reproduce with a modified dtest. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19491) decommissioned nodes show as UNREACHABLE in describecluster afterward
[ https://issues.apache.org/jira/browse/CASSANDRA-19491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-19491: - Fix Version/s: 5.0.x (was: 5.0-rc) > decommissioned nodes show as UNREACHABLE in describecluster afterward > - > > Key: CASSANDRA-19491 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19491 > Project: Cassandra > Issue Type: Bug > Components: Cluster/Membership >Reporter: Brandon Williams >Priority: Normal > Fix For: 4.1.x, 5.0.x > > > [~urandom] noticed this happening in his cluster and I have been able to > reproduce with a modified dtest. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19491) decommissioned nodes show as UNREACHABLE in describecluster afterward
[ https://issues.apache.org/jira/browse/CASSANDRA-19491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-19491: - Bug Category: Parent values: Correctness(12982) Complexity: Normal Component/s: Cluster/Membership Discovered By: User Report Fix Version/s: 4.1.x 5.0-rc Severity: Normal Status: Open (was: Triage Needed) Eric's cluster is on 4.1, I have repro'd against 5.0 > decommissioned nodes show as UNREACHABLE in describecluster afterward > - > > Key: CASSANDRA-19491 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19491 > Project: Cassandra > Issue Type: Bug > Components: Cluster/Membership >Reporter: Brandon Williams >Priority: Normal > Fix For: 4.1.x, 5.0-rc > > > [~urandom] noticed this happening in his cluster and I have been able to > reproduce with a modified dtest. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
