[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cassandra-commits
Subject:    [jira] [Commented] (CASSANDRA-7510) Notify clients that bootstrap is finished over binary protocol
From:       "Tyler Hobbs (JIRA)" <jira () apache ! org>
Date:       2014-10-31 20:25:34
Message-ID: JIRA.12725949.1404801031000.385530.1414787134858 () Atlassian ! JIRA
[Download RAW message or body]


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

Tyler Hobbs commented on CASSANDRA-7510:
----------------------------------------

Well, this is definitely an improvement over what we currently have, so I'll +1 \
committing this for now and open a new ticket to figure out the best way to delay UP \
notifications until the rpc server has started.

> 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
> Assignee: Brandon Williams
> Priority: Minor
> Fix For: 2.0.12
> 
> 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 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.3.4#6332)


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic