[
https://issues.apache.org/jira/browse/CASSANDRA-8494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14249082#comment-14249082
]
Yuki Morishita commented on CASSANDRA-8494:
-------------------------------------------
I think streaming part is not a big deal. More work is needed for announcing
available token.
Also, we need to define behavior of bootstrap failure.
If one part of bootstrap failed, it is better to be able to re-bootstrap only
the failed part.
To do this, we need to have rich bootstrap state management and new API? to
resume bootstrapping.
> incremental bootstrap
> ---------------------
>
> Key: CASSANDRA-8494
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8494
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Jon Haddad
> Priority: Minor
> Labels: density
>
> Current bootstrapping involves (to my knowledge) picking tokens and streaming
> data before the node is available for requests. This can be problematic with
> "fat nodes", since it may require 20TB of data to be streamed over before the
> machine can be useful. This can result in a massive window of time before
> the machine can do anything useful.
> As a potential approach to mitigate the huge window of time before a node is
> available, I suggest modifying the bootstrap process to only acquire a single
> initial token before being marked UP. This would likely be a configuration
> parameter "incremental_bootstrap" or something similar.
> After the node is bootstrapped with this one token, it could go into UP
> state, and could then acquire additional tokens (one or a handful at a time),
> which would be streamed over while the node is active and serving requests.
> The benefit here is that with the default 256 tokens a node could become an
> active part of the cluster with less than 1% of it's final data streamed over.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
