cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Deleted] (CASSANDRA-8236) Delay "node up" and "node added" notifications until native protocol server is started
Date Sat, 15 Nov 2014 17:55:33 GMT

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

Aleksey Yeschenko updated CASSANDRA-8236:
-----------------------------------------
    Comment: was deleted

(was: SPARK-4427
please work on it
Thanks ...............
)

> Delay "node up" and "node added" notifications until native protocol server is started
> --------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-8236
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8236
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Tyler Hobbs
>            Assignee: Brandon Williams
>             Fix For: 3.0
>
>         Attachments: 8236.txt
>
>
> As discussed in CASSANDRA-7510, there is still a gap between when a "node up" or "node
added" notification may be sent to native protocol clients (in response to a gossip event)
and when the native protocol server is ready to serve requests.
> Everything in between the call to {{StorageService.instance.initServer()}} and creation
of the native server in {{CassandraDaemon.setup()}} contributes to this delay, but waiting
for Gossip to settle introduces the biggest delay.
> We may need to introduce a "STARTING" gossip state for the period inbetween, which is
why this is scheduled for 3.0.  If there's a better option, though, it may make sense to put
this in 2.1.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message