You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jeremy Hanna (JIRA)" <ji...@apache.org> on 2019/06/04 21:24:00 UTC
[jira] [Updated] (CASSANDRA-15095) Split Gossiper into separate
interfaces
[ https://issues.apache.org/jira/browse/CASSANDRA-15095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Hanna updated CASSANDRA-15095:
-------------------------------------
Component/s: Cluster/Gossip
> Split Gossiper into separate interfaces
> ---------------------------------------
>
> Key: CASSANDRA-15095
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15095
> Project: Cassandra
> Issue Type: Improvement
> Components: Cluster/Gossip
> Reporter: Blake Eggleston
> Priority: Normal
>
> As [~aweisberg] suggests [here|https://issues.apache.org/jira/browse/CASSANDRA-15059?focusedCommentId=16802986&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16802986], a better way to encourage Gossiper threadsafety would be to split it into interfaces depending on which methods are safe to be called from where. At minimum, one for outside the gossiper stage, on for inside.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org