cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joost Reuzel (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7510) Notify clients that bootstrap is finished over binary protocol
Date Thu, 10 Jul 2014 19:49:04 GMT


Joost Reuzel commented on CASSANDRA-7510:

Small additional question on this from a client programmer: Does the proposed change of sending
the STATUS_NORMAL state later also mean that until that time the node does not show up in
the system.peers table? The bootstrap process can take quite some time, and when a client
is started, it will typically inspect the system.peers table for other nodes to contact. It
would be great if a bootstrapping node is not (yet) available there, as a fresh client instance
will otherwise encounter the same issue as reported above. 

Finally, it would be great if the current up/down(/bootstrapping) status is noted in the system.peers
table so a client does not have to find out the hard way, but I suppose that may be another
JIRA item.

Thanks for the excellent support

> Notify clients that bootstrap is finished over binary protocol
> --------------------------------------------------------------
>                 Key: CASSANDRA-7510
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Joost Reuzel
>            Priority: Minor
>             Fix For: 2.0.10
>         Attachments: 7510.txt
> 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
> 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

View raw message