cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7510) Notify clients that bootstrap is finished over binary protocol
Date Tue, 08 Jul 2014 10:46:06 GMT

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

Sylvain Lebresne commented on CASSANDRA-7510:
---------------------------------------------

bq. My proposal would be to send an additional UP event when the bootstrap is done

Frankly, I never intended the onAdd notification to be sent before the bootstrap, it's more
a bug that never got fixed. Imo, it doesn't make a whole lot of sense to notify client at
all until a node has been properly boostrapped, so I would *strongly* prefer just fixing onAdd
notifications so it's send only when the node is ready. Similarly, onUp is actually sent before
the the native protocol server has been initialized because there is currently no proper place
to do it. So really, what we should fix is that onAdd/onUp events for a given node should
only be sent when the node in question is ready to receive connection on the native protocol
server. This might require adding an additional gossip state/message so a node advertise when
the protocol server is up and ready. 

> 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: Improvement
>            Reporter: Joost Reuzel
>
> 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