Re: bootstrapping new nodes on 1.2.12

2014-07-30 Thread Mark Reddy
Hi Parag, 1) Would anyone be able to help me interrupt this information from OpsCenter? At a high level bootstrapping a new node has two phases, streaming and secondary index builds. I believe OpsCenter will only report active streams, the pending stream will be listed as such in

RE: bootstrapping new nodes on 1.2.12

2014-07-30 Thread Parag Patel
particular order? Perhaps this is a coincidence, but if I were to sort my hostnames in alphabetical order, it’s currently streaming from the last 2. From: Mark Reddy [mailto:mark.re...@boxever.com] Sent: Wednesday, July 30, 2014 4:42 AM To: user@cassandra.apache.org Subject: Re: bootstrapping new

Re: bootstrapping new nodes on 1.2.12

2014-07-30 Thread Mark Reddy
. *From:* Mark Reddy [mailto:mark.re...@boxever.com] *Sent:* Wednesday, July 30, 2014 4:42 AM *To:* user@cassandra.apache.org *Subject:* Re: bootstrapping new nodes on 1.2.12 Hi Parag, 1) Would anyone be able to help me interrupt this information from OpsCenter? At a high level

RE: bootstrapping new nodes on 1.2.12

2014-07-30 Thread Parag Patel
it such that full GC’s don’t impact bootstrapping? Should we increase phi_convict_threshold ? Parag From: Mark Reddy [mailto:mark.re...@boxever.com] Sent: Wednesday, July 30, 2014 7:58 AM To: user@cassandra.apache.org Subject: Re: bootstrapping new nodes on 1.2.12 Thanks for the detailed response. I

Re: bootstrapping new nodes on 1.2.12

2014-07-30 Thread Mark Reddy
: bootstrapping new nodes on 1.2.12 Thanks for the detailed response. I checked ‘nodetool netstats’ and I see there are pending streams, all of which are stuck at 0%. I was expecting to see at least one output that was more than 0%. Have you seen this before? This could indicate

RE: bootstrapping new nodes on 1.2.12

2014-07-30 Thread Parag Patel
[mailto:mark.re...@boxever.com] Sent: Wednesday, July 30, 2014 9:06 AM To: user@cassandra.apache.org Subject: Re: bootstrapping new nodes on 1.2.12 HI Parag, I see this output my log many times over for 2 nodes. We have a cron entry across all clusters that force a full GC at 2 AM. node1 is due to Full

Re: bootstrapping new nodes on 1.2.12

2014-07-30 Thread Mark Reddy
Reddy [mailto:mark.re...@boxever.com] *Sent:* Wednesday, July 30, 2014 9:06 AM *To:* user@cassandra.apache.org *Subject:* Re: bootstrapping new nodes on 1.2.12 HI Parag, I see this output my log many times over for 2 nodes. We have a cron entry across all clusters that force a full GC

RE: bootstrapping new nodes on 1.2.12

2014-07-30 Thread Parag Patel
:31:20 - handshaking version with Node1 because failed previously 9:31:37 - Node2 – detects Node1 UP From: Mark Reddy [mailto:mark.re...@boxever.com] Sent: Wednesday, July 30, 2014 9:41 AM To: user@cassandra.apache.org Subject: Re: bootstrapping new nodes on 1.2.12 Our Full GC’s take about 9

bootstrapping new nodes on 1.2.12

2014-07-29 Thread Parag Patel
Hi, It's taking a while to boostrap a 13th node into a 12 node cluster. The average node size is about 1.7TB. At the beginning of today we were close to .9TB on the new node and 12 hours later we're at 1.1TB. I figured it would have finished by now because when I was looking on OpsCenter,