[CASSANDRA-8494] incremental bootstrap

• Type: New Feature
• Status: In Progress
• Priority: Low
• Resolution: Unresolved
• Fix Version/s: 5.x
• Component/s: Legacy/Streaming and Messaging
• Labels: dense-storage
• Assignee: Yuki Morishita
• Reporter: Jon Haddad

Authors

Yuki Morishita

• Created: 16/Dec/14 19:34
• Updated: 07/Mar/23 10:53

Description

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.

Issue Links

• relates to: CASSANDRA-8523 Writes should be sent to a replacement node which has a new IP while it is streaming in data
• relates to: CASSANDRA-8591 Tunable bootstrapping
• requires: CASSANDRA-16141 Enable Adding and Removing Tokens to a Node (Dynamic Virtual Nodes)

Sub-Tasks

• Resumable bootstrap streaming: Resolved
• Keep node up even when bootstrap is failed (and provide tool to resume bootstrap): Resolved
• Accept reads while bootstrapping for available ranges: Open