Re: Bootstrap Timing

2014-04-25 Thread Steven A Robenalt
Interesting. I did our 2.0.3 -> 2.0.5 upgrade by bootstrapping/joining each node into our cluster, one at a time, then retiring the old nodes one at a time. Maybe something specific to the 2.0.6 release? Good to hear that you've gotten through it anyway. Steve On Fri, Apr 25, 2014 at 7:49 AM,

Re: Bootstrap Timing

2014-04-25 Thread Phil Burress
Cassandra 2.0.6 On Fri, Apr 25, 2014 at 10:31 AM, James Rothering wrote: > What version of C* is this? > > > On Fri, Apr 25, 2014 at 6:55 AM, Phil Burress wrote: > >> Just a follow-up on this for any interested parties. Ultimately we've >> determined that the bootstrap/join process is broken in

Re: Bootstrap Timing

2014-04-25 Thread James Rothering
What version of C* is this? On Fri, Apr 25, 2014 at 6:55 AM, Phil Burress wrote: > Just a follow-up on this for any interested parties. Ultimately we've > determined that the bootstrap/join process is broken in Cassandra. We ended > up creating an entirely new cluster and migrating the data. > >

Re: Bootstrap Timing

2014-04-25 Thread Phil Burress
Just a follow-up on this for any interested parties. Ultimately we've determined that the bootstrap/join process is broken in Cassandra. We ended up creating an entirely new cluster and migrating the data. On Mon, Apr 21, 2014 at 10:32 AM, Phil Burress wrote: > The new node has managed to stay u

Re: Bootstrap Timing

2014-04-21 Thread Phil Burress
The new node has managed to stay up without dying for about 24 hours now... but it still is in JOINING state. A new concern has popped up. Disk usage is at 500GB on the new node. The three original nodes have about 40GB each. Any ideas why this is happening? On Sat, Apr 19, 2014 at 9:19 PM, Phil

Re: Bootstrap Timing

2014-04-19 Thread Phil Burress
Thank you all for your advice and good info. The node has died a couple of times with out of memory errors. I've restarted each time but it starts re - running compaction and then dies again. Is there a better way to do this? On Apr 18, 2014 6:06 PM, "Steven A Robenalt" wrote: > That's what I'd

Re: Bootstrap Timing

2014-04-18 Thread Steven A Robenalt
That's what I'd be doing, but I wouldn't expect it to run for 3 days this time. My guess is that whatever was going wrong with the bootstrap when you had 3 nodes starting at once was interfering with the completion of the 1 remaining node of those 3. A clean bootstrap of a single node should comple

Re: Bootstrap Timing

2014-04-18 Thread Phil Burress
First, I just stopped 2 of the nodes and left one running. But this morning, I stopped that third node, cleared out the data, restarted and let it rejoin again. It appears streaming is done (according to netstats), right now it appears to be running compaction and building secondary index (accordin

Re: Bootstrap Timing

2014-04-18 Thread Steven A Robenalt
Looking back through this email chain, it looks like Phil said he wasn't using vnodes. For the record, we are using vnodes since we brought up our first cluster, and have not seen any issues with bootstrapping new nodes either to replace existing nodes, or to grow/shrink the cluster. We did adhere

Re: Bootstrap Timing

2014-04-18 Thread Robert Coli
On Fri, Apr 18, 2014 at 5:05 AM, Phil Burress wrote: > nodetool netstats shows 84 files. They are all at 100%. Nothing showing in > Pending or Active for Read Repair Stats. > > I'm assuming this means it's done. But it still shows "JOINING". Is there > an undocumented step I'm missing here? This w

Re: Bootstrap Timing

2014-04-18 Thread Mark Reddy
If all streams have completed, the node could be still rebuilding secondary indexes? Try looking at 'nodetool compactionstats' for this. On Fri, Apr 18, 2014 at 1:05 PM, Phil Burress wrote: > nodetool netstats shows 84 files. They are all at 100%. Nothing showing in > Pending or Active for Read

Re: Bootstrap Timing

2014-04-18 Thread Phil Burress
nodetool netstats shows 84 files. They are all at 100%. Nothing showing in Pending or Active for Read Repair Stats. I'm assuming this means it's done. But it still shows "JOINING". Is there an undocumented step I'm missing here? This whole process seems broken to me. On Thu, Apr 17, 2014 at 4:32

Re: Bootstrap Timing

2014-04-17 Thread Robert Coli
On Wed, Apr 16, 2014 at 1:56 PM, Phil Burress wrote: > I've shut down two of the nodes and am bootstrapping one right now. Is > there any way to tell when it will finish bootstrapping? > "nodetool netstats" will show the progress of the streams involved, which could help you estimate. =Rob

Re: Bootstrap Timing

2014-04-16 Thread Phil Burress
I've shut down two of the nodes and am bootstrapping one right now. Is there any way to tell when it will finish bootstrapping? On Wed, Apr 16, 2014 at 2:56 PM, Phil Burress wrote: > Thanks! > > > On Wed, Apr 16, 2014 at 2:50 PM, Robert Coli wrote: > >> On Wed, Apr 16, 2014 at 11:16 AM, Phil Bu

Re: Bootstrap Timing

2014-04-16 Thread Phil Burress
Thanks! On Wed, Apr 16, 2014 at 2:50 PM, Robert Coli wrote: > On Wed, Apr 16, 2014 at 11:16 AM, Phil Burress > wrote: > >> Thanks very much for the response. I'm not using vnodes, does that >> matter? >> > > Not in your case. In some cases it is safe to bootstrap multiple nodes > into a cluste

Re: Bootstrap Timing

2014-04-16 Thread Robert Coli
On Wed, Apr 16, 2014 at 11:16 AM, Phil Burress wrote: > Thanks very much for the response. I'm not using vnodes, does that matter? > Not in your case. In some cases it is safe to bootstrap multiple nodes into a cluster at once AT SPECIFIC TOKENS, because there is more than one replica set to boot

Re: Bootstrap Timing

2014-04-16 Thread Ken Hancock
Seed nodes don't bootstrap. https://issues.apache.org/jira/browse/CASSANDRA-5836 On Wed, Apr 16, 2014 at 2:17 PM, Phil Burress wrote: > Also, one more quick question. For the new nodes, do I add all three > existing nodes as seeds? Or just add one? > > > On Wed, Apr 16, 2014 at 2:16 PM, Phil

Re: Bootstrap Timing

2014-04-16 Thread Phil Burress
Also, one more quick question. For the new nodes, do I add all three existing nodes as seeds? Or just add one? On Wed, Apr 16, 2014 at 2:16 PM, Phil Burress wrote: > Thanks very much for the response. I'm not using vnodes, does that matter? > > > On Wed, Apr 16, 2014 at 2:13 PM, Robert Coli wro

Re: Bootstrap Timing

2014-04-16 Thread Phil Burress
Thanks very much for the response. I'm not using vnodes, does that matter? On Wed, Apr 16, 2014 at 2:13 PM, Robert Coli wrote: > On Wed, Apr 16, 2014 at 11:10 AM, Phil Burress > wrote: > >> How long does bootstrapping typically take? I have 3 existing nodes in >> our cluster with about 40GB ea

Re: Bootstrap Timing

2014-04-16 Thread Robert Coli
On Wed, Apr 16, 2014 at 11:10 AM, Phil Burress wrote: > How long does bootstrapping typically take? I have 3 existing nodes in our > cluster with about 40GB each. I've added three new nodes to the cluster. > They have been in bootstrap mode for a little over 3 days now. Should I be > concerned? Is

Bootstrap Timing

2014-04-16 Thread Phil Burress
Greetings, How long does bootstrapping typically take? I have 3 existing nodes in our cluster with about 40GB each. I've added three new nodes to the cluster. They have been in bootstrap mode for a little over 3 days now. Should I be concerned? Is there a way to tell how long it will take to finis