cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Svihla (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8494) incremental bootstrap
Date Tue, 16 Dec 2014 21:54:13 GMT


Ryan Svihla commented on CASSANDRA-8494:

I'm mixed on the push for density, I get that people _really_ want it, and this would substantially
help Cassandra in that space, but I'm also convinced just by physics the story for high density
will always be worse than the story for a bunch of cheap low density nodes (IE total cost,
not just data center space costs).

Regardless, i think even in the case of more say 1TB nodes, this would be an impressive boost
to handling overloaded clusters, where load can be moved off struggling nodes more quickly
and gracefully. What we struggle with today in the field is a people that don't monitor their
clusters, and don't realize till they're going OOM that they're in trouble. For those folks
we always struggle streaming in new nodes as quickly as possible. I think this could potentially
really help with those more common than you'd think scenarios.

> incremental bootstrap
> ---------------------
>                 Key: CASSANDRA-8494
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jon Haddad
>            Priority: Minor
> 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
> 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

View raw message