+1 On Fri, Apr 2, 2010 at 3:49 PM, Jonathan Ellis <jbel...@gmail.com> wrote:
> Ah, right. That's confusing for everyone. I think the best solution > there is to just get > http://issues.apache.org/jira/browse/CASSANDRA-579 done so it can > start streaming immediately. > > On Fri, Apr 2, 2010 at 5:45 PM, Dan Di Spaltro <dan.dispal...@gmail.com> > wrote: > > It did once it was actually done anti-compacting. The biggest > > question-mark (for us) was, what was happening during the > > anti-compaction phase. > > > > On Fri, Apr 2, 2010 at 3:39 PM, Jonathan Ellis <jbel...@gmail.com> > wrote: > >> Great, glad it worked. > >> > >> Sounds like we do have a bug though if the destination node never > >> showed anything in Streaming mbean. :( > >> > >> On Fri, Apr 2, 2010 at 5:11 PM, Dan Di Spaltro <dan.dispal...@gmail.com> > wrote: > >>> To close the loop on this, the node finished bootstrapping. The > >>> source node rebooting definitely halted the process. > >>> > >>> Visibility-wise, watching the anti-compactions is the best way to tell > >>> how much progress is being made on the bootstrapping process. The > >>> CompactionManager mbean gives you insight into the progress of each > >>> anti-compaction as well. > >>> > >>> Thanks for the help, > >>> > >>> On Thu, Apr 1, 2010 at 4:23 PM, Jonathan Ellis <jbel...@gmail.com> > wrote: > >>>> I would turn debug logging on globally on the new node, that will > >>>> answer more questions than just the streaming package. > >>>> > >>> > >>> > >>> > >>> -- > >>> Dan Di Spaltro > >>> > >> > > > > > > > > -- > > Dan Di Spaltro > > > -- Chris Goffinet
