[jira] [Updated] (CASSANDRA-21035) Nodes with LEFT state do not get expired from gossip
[ https://issues.apache.org/jira/browse/CASSANDRA-21035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe updated CASSANDRA-21035: Since Version: NA Source Control Link: https://github.com/apache/cassandra/commit/ad3f0e8f412707f3ace2ae3c41b43aadb853cb82 Resolution: Fixed Status: Resolved (was: Ready to Commit) > Nodes with LEFT state do not get expired from gossip > > > Key: CASSANDRA-21035 > URL: https://issues.apache.org/jira/browse/CASSANDRA-21035 > Project: Apache Cassandra > Issue Type: Bug > Components: Cluster/Gossip >Reporter: Sam Tunnicliffe >Assignee: Sam Tunnicliffe >Priority: Normal > Fix For: 6.x > > Attachments: ci_summary.html, result_details.tar.gz > > > When a node is removed from the cluster via > decommission/removenode/assassinate it is transitioned to a LEFT status in > gossip. For historical reasons, this state is intended to persist in gossip > for some period (default is 72hrs) before being expunged. Since CEP-21, > gossip status is no longer used for anything significant by C* itself, but > this behaviour was preserved in case any tooling was relying on it. However, > there is a bug in that the purging from gossip after 72 hrs is not occurring > correctly. From the perspective of C* itself this is harmless, but it will > eventually lead to gossip state being oversized. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
[jira] [Updated] (CASSANDRA-21035) Nodes with LEFT state do not get expired from gossip
[ https://issues.apache.org/jira/browse/CASSANDRA-21035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-21035: Reviewers: Marcus Eriksson, Marcus Eriksson (was: Marcus Eriksson) Marcus Eriksson, Marcus Eriksson (was: Marcus Eriksson) Status: Review In Progress (was: Patch Available) > Nodes with LEFT state do not get expired from gossip > > > Key: CASSANDRA-21035 > URL: https://issues.apache.org/jira/browse/CASSANDRA-21035 > Project: Apache Cassandra > Issue Type: Bug > Components: Cluster/Gossip >Reporter: Sam Tunnicliffe >Assignee: Sam Tunnicliffe >Priority: Normal > Fix For: 6.x > > Attachments: ci_summary.html, result_details.tar.gz > > > When a node is removed from the cluster via > decommission/removenode/assassinate it is transitioned to a LEFT status in > gossip. For historical reasons, this state is intended to persist in gossip > for some period (default is 72hrs) before being expunged. Since CEP-21, > gossip status is no longer used for anything significant by C* itself, but > this behaviour was preserved in case any tooling was relying on it. However, > there is a bug in that the purging from gossip after 72 hrs is not occurring > correctly. From the perspective of C* itself this is harmless, but it will > eventually lead to gossip state being oversized. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
[jira] [Updated] (CASSANDRA-21035) Nodes with LEFT state do not get expired from gossip
[ https://issues.apache.org/jira/browse/CASSANDRA-21035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-21035: Status: Ready to Commit (was: Review In Progress) +1 > Nodes with LEFT state do not get expired from gossip > > > Key: CASSANDRA-21035 > URL: https://issues.apache.org/jira/browse/CASSANDRA-21035 > Project: Apache Cassandra > Issue Type: Bug > Components: Cluster/Gossip >Reporter: Sam Tunnicliffe >Assignee: Sam Tunnicliffe >Priority: Normal > Fix For: 6.x > > Attachments: ci_summary.html, result_details.tar.gz > > > When a node is removed from the cluster via > decommission/removenode/assassinate it is transitioned to a LEFT status in > gossip. For historical reasons, this state is intended to persist in gossip > for some period (default is 72hrs) before being expunged. Since CEP-21, > gossip status is no longer used for anything significant by C* itself, but > this behaviour was preserved in case any tooling was relying on it. However, > there is a bug in that the purging from gossip after 72 hrs is not occurring > correctly. From the perspective of C* itself this is harmless, but it will > eventually lead to gossip state being oversized. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
[jira] [Updated] (CASSANDRA-21035) Nodes with LEFT state do not get expired from gossip
[ https://issues.apache.org/jira/browse/CASSANDRA-21035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe updated CASSANDRA-21035: Reviewers: Marcus Eriksson > Nodes with LEFT state do not get expired from gossip > > > Key: CASSANDRA-21035 > URL: https://issues.apache.org/jira/browse/CASSANDRA-21035 > Project: Apache Cassandra > Issue Type: Bug > Components: Cluster/Gossip >Reporter: Sam Tunnicliffe >Assignee: Sam Tunnicliffe >Priority: Normal > Fix For: 6.x > > Attachments: ci_summary.html, result_details.tar.gz > > > When a node is removed from the cluster via > decommission/removenode/assassinate it is transitioned to a LEFT status in > gossip. For historical reasons, this state is intended to persist in gossip > for some period (default is 72hrs) before being expunged. Since CEP-21, > gossip status is no longer used for anything significant by C* itself, but > this behaviour was preserved in case any tooling was relying on it. However, > there is a bug in that the purging from gossip after 72 hrs is not occurring > correctly. From the perspective of C* itself this is harmless, but it will > eventually lead to gossip state being oversized. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
[jira] [Updated] (CASSANDRA-21035) Nodes with LEFT state do not get expired from gossip
[ https://issues.apache.org/jira/browse/CASSANDRA-21035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe updated CASSANDRA-21035: Attachment: ci_summary.html result_details.tar.gz > Nodes with LEFT state do not get expired from gossip > > > Key: CASSANDRA-21035 > URL: https://issues.apache.org/jira/browse/CASSANDRA-21035 > Project: Apache Cassandra > Issue Type: Bug > Components: Cluster/Gossip >Reporter: Sam Tunnicliffe >Assignee: Sam Tunnicliffe >Priority: Normal > Fix For: 6.x > > Attachments: ci_summary.html, result_details.tar.gz > > > When a node is removed from the cluster via > decommission/removenode/assassinate it is transitioned to a LEFT status in > gossip. For historical reasons, this state is intended to persist in gossip > for some period (default is 72hrs) before being expunged. Since CEP-21, > gossip status is no longer used for anything significant by C* itself, but > this behaviour was preserved in case any tooling was relying on it. However, > there is a bug in that the purging from gossip after 72 hrs is not occurring > correctly. From the perspective of C* itself this is harmless, but it will > eventually lead to gossip state being oversized. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
[jira] [Updated] (CASSANDRA-21035) Nodes with LEFT state do not get expired from gossip
[ https://issues.apache.org/jira/browse/CASSANDRA-21035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe updated CASSANDRA-21035: Test and Documentation Plan: New dtests added Status: Patch Available (was: Open) > Nodes with LEFT state do not get expired from gossip > > > Key: CASSANDRA-21035 > URL: https://issues.apache.org/jira/browse/CASSANDRA-21035 > Project: Apache Cassandra > Issue Type: Bug > Components: Cluster/Gossip >Reporter: Sam Tunnicliffe >Assignee: Sam Tunnicliffe >Priority: Normal > Fix For: 6.x > > > When a node is removed from the cluster via > decommission/removenode/assassinate it is transitioned to a LEFT status in > gossip. For historical reasons, this state is intended to persist in gossip > for some period (default is 72hrs) before being expunged. Since CEP-21, > gossip status is no longer used for anything significant by C* itself, but > this behaviour was preserved in case any tooling was relying on it. However, > there is a bug in that the purging from gossip after 72 hrs is not occurring > correctly. From the perspective of C* itself this is harmless, but it will > eventually lead to gossip state being oversized. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
[jira] [Updated] (CASSANDRA-21035) Nodes with LEFT state do not get expired from gossip
[ https://issues.apache.org/jira/browse/CASSANDRA-21035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe updated CASSANDRA-21035: Bug Category: Parent values: Correctness(12982)Level 1 values: API / Semantic Implementation(12988) Complexity: Normal Discovered By: User Report Fix Version/s: 6.x Severity: Normal Status: Open (was: Triage Needed) > Nodes with LEFT state do not get expired from gossip > > > Key: CASSANDRA-21035 > URL: https://issues.apache.org/jira/browse/CASSANDRA-21035 > Project: Apache Cassandra > Issue Type: Bug > Components: Cluster/Gossip >Reporter: Sam Tunnicliffe >Assignee: Sam Tunnicliffe >Priority: Normal > Fix For: 6.x > > > When a node is removed from the cluster via > decommission/removenode/assassinate it is transitioned to a LEFT status in > gossip. For historical reasons, this state is intended to persist in gossip > for some period (default is 72hrs) before being expunged. Since CEP-21, > gossip status is no longer used for anything significant by C* itself, but > this behaviour was preserved in case any tooling was relying on it. However, > there is a bug in that the purging from gossip after 72 hrs is not occurring > correctly. From the perspective of C* itself this is harmless, but it will > eventually lead to gossip state being oversized. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
