[jira] [Resolved] (CASSANDRA-13713) Move processing of EchoMessage response to gossip stage

["Jason Brown (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-13713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Brown resolved CASSANDRA-13713.
-------------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 4.x)
                   4.0

Decided to be very cautious and only committed to trunk (4.0) as sha {{674addd03701abf1bce7d6b47978761c00d0a431}}

> Move processing of EchoMessage response to gossip stage
> -------------------------------------------------------
>
>                 Key: CASSANDRA-13713
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13713
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Distributed Metadata
>            Reporter: Jason Brown
>            Assignee: Jason Brown
>            Priority: Minor
>             Fix For: 4.0
>
>
> Currently, when a node receives an {{EchoMessage}}, is sends a simple ACK reply back (see {{EchoVerbHandler}}). The ACK is sent on the small message connection, and because it is 'generically' typed as {{Verb.REQUEST_RESPONSE}}, is consumed on a {{Stage.REQUEST_RESPONSE}} thread. The proper thread for this response to be consumed is {{Stage.GOSSIP}}, that way we can move more of the updating of the gossip state to a single, centralized thread, and less abuse of gossip's shared mutable state can occur.



--
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