cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7510) Notify clients that bootstrap is finished over binary protocol
Date Wed, 09 Jul 2014 12:35:04 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-7510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056171#comment-14056171
] 

Brandon Williams commented on CASSANDRA-7510:
---------------------------------------------

We shouldn't need a new gossip state for this, I think what you want to do is change the onJoinCluster
notification you're doing in SS.onAlive to actually be in SS.handleStateNormal, sort of like
you do for sending onMove, except when the node hasn't moved.  Going to normal is the "I'm
ready" message already.

> Notify clients that bootstrap is finished over binary protocol
> --------------------------------------------------------------
>
>                 Key: CASSANDRA-7510
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7510
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Joost Reuzel
>            Priority: Minor
>             Fix For: 2.0.10
>
>
> Currently, Cassandra will notify clients when a new node is added to a cluster. However,
that node is typically not usable yet. It first needs to gossip its key range and finish loading
all its assigned data before it allows clients to connect. Depending on the amount of data
this may take quite a while. The clients in the mean time have no clue about the bootstrap
status of that node. The only thing they can do is periodically check if it will accept a
connection. 
> My proposal would be to send an additional UP event when the bootstrap is done, this
allows clients to mark the node initially as down/unavailable and simply wait for the UP event
to arrive.
> Kind regards,
> Joost



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message