Thanks, is there any way to determine that rebuild is complete.
Based on following line in StorageService.java, it's not logged. So, any other
way to check besides checking data size through nodetool status ?
finally
{
// rebuild is done (successfully or not)
isRebuilding.set(false);
}
-----Original Message-----
From: Eric Evans [mailto:[email protected]]
Sent: Thursday, March 31, 2016 9:50 AM
To: [email protected]
Subject: Re: Speeding up "nodetool rebuild"
On Wed, Mar 30, 2016 at 3:44 PM, Anubhav Kale <[email protected]>
wrote:
> Any other ways to make the “rebuild” faster ?
TL;DR add more nodes
If you're encountering a per-stream bottleneck (easy to do if using
compression), then having a higher node count will translate to higher stream
concurrency, and greater throughput.
Another thing to keep in mind, the streamthroughput value is *outbound*, it
doesn't matter what you have that set to on the rebuilding/bootstrapping node,
it *does* matter what it is set to on the nodes that are sending to it
(https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissues.apache.org%2fjira%2fbrowse%2fCASSANDRA-11303&data=01%7c01%7cAnubhav.Kale%40microsoft.com%7c27fd8203aa364253b6fc08d3598493a8%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=rnPHvE12p04CnRXkHgD%2bkllLOqGA4gnlSuM3QsCTpDE%3d
aims to introduce an inbound tunable though).
--
Eric Evans
[email protected]
