[
https://issues.apache.org/jira/browse/CASSANDRA-2961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096117#comment-13096117
]
Jérémy Sevellec commented on CASSANDRA-2961:
--------------------------------------------
I agree with you about the fact that : REMOVED_TOKEN and STATUS_LEFT are the
only states we need to worry about expiring.
But if SS :
- first receive a change for an endpoint with the status by REMOVED_TOKEN or
STATUS_LEFT
- and then for this same endpoint receiving an other change with one of other
status
we have to delete the expireTime because the gossiper will remove this endpoint
when expireTime will be exceeded and it must not? no?
> Expire dead gossip states based on time
> ---------------------------------------
>
> Key: CASSANDRA-2961
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2961
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Brandon Williams
> Fix For: 1.0
>
>
> Currently dead states are held until aVeryLongTime, 3 days. The problem is
> that if a node reboots within this period, it begins a new 3 days and will
> repopulate the ring with the dead state. While mostly harmless, perpetuating
> the state forever is at least wasting a small amount of bandwidth. Instead,
> we can expire states based on a ttl, which will require that the cluster be
> loosely time synced; within the quarantine period of 60s.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
