Thanks. Would it be better to log it clearly or expose as a metric or something else that can be easily automated ?
From: Alain RODRIGUEZ [mailto:arodr...@gmail.com] Sent: Friday, April 1, 2016 1:55 AM To: user@cassandra.apache.org Subject: Re: Speeding up "nodetool rebuild" Hi, is there any way to determine that rebuild is complete If you ran it from a screen (https://www.gnu.org/software/screen/manual/screen.html<https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fwww.gnu.org%2fsoftware%2fscreen%2fmanual%2fscreen.html&data=01%7c01%7cAnubhav.Kale%40microsoft.com%7c83413eba6d6a41c15a4608d35a0b5741%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=iCdh%2bCaOTY%2fF5KBQtPhRrKKKYAzXasMu0LsiiVoNHs0%3d>) or similar stuff, you should see the command return. Also, 'nodetool netstats | grep -v 100%' will show you remaining stream. No stream = rebuild finish (look for possible errors in the logs though...). Last tip is you should be able to imagine how big the dataset is going to be and checking the on disk size give good progress information too. This is not really accurate though. C*heers, ----------------------- Alain Rodriguez - al...@thelastpickle.com<mailto:al...@thelastpickle.com> France The Last Pickle - Apache Cassandra Consulting http://www.thelastpickle.com<https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fwww.thelastpickle.com&data=01%7c01%7cAnubhav.Kale%40microsoft.com%7c83413eba6d6a41c15a4608d35a0b5741%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=nt4LvhgsIHTb2IyfYGwDSy3%2biaTslE4%2ffNLfGTgAExs%3d> 2016-03-31 23:19 GMT+02:00 Anubhav Kale <anubhav.k...@microsoft.com<mailto:anubhav.k...@microsoft.com>>: 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:eev...@wikimedia.org<mailto:eev...@wikimedia.org>] Sent: Thursday, March 31, 2016 9:50 AM To: user@cassandra.apache.org<mailto:user@cassandra.apache.org> Subject: Re: Speeding up "nodetool rebuild" On Wed, Mar 30, 2016 at 3:44 PM, Anubhav Kale <anubhav.k...@microsoft.com<mailto:anubhav.k...@microsoft.com>> 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 eev...@wikimedia.org<mailto:eev...@wikimedia.org>
