[
https://issues.apache.org/jira/browse/CASSANDRA-8494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17928912#comment-17928912
]
Jon Haddad commented on CASSANDRA-8494:
---------------------------------------
[~paulo] I closed this because if we implement incremental bootstrap on TCM,
it would be a completely separate body of work, and having a single JIRA for
two completely different implementations and work history would be confusing.
However, if you think it's better to keep this open, it's fine with me. Feel
free to reopen if it makes sense to you.
> incremental bootstrap
> ---------------------
>
> Key: CASSANDRA-8494
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8494
> Project: Apache Cassandra
> Issue Type: New Feature
> Components: Legacy/Streaming and Messaging
> Reporter: Jon Haddad
> Assignee: Yuki Morishita
> Priority: Low
> Labels: dense-storage
> Fix For: 5.x
>
>
> 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
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
