The next time you encounter such a problem, check with JMX whether any compactions are pending on the sending node. Compaction and anticompaction are run in the same stage IIRC, so when a long-running compaction is in progress, all anticompaction on the same node has to wait.
Martin > -----Original Message----- > From: Aaron Lav [mailto:a...@pobox.com] > Sent: Friday, June 04, 2010 9:52 PM > To: user@cassandra.apache.org > Cc: a...@pobox.com > Subject: Re: Expected wait while bootstrapping? > > On Fri, Jun 04, 2010 at 12:35:51PM -0700, Gary Dusbabek wrote: > > Most of the streaming messages are DEBUG, so you'll have to > amp up logging. > > I've upped logging on the bootstrapping node, and I realize > that it's trying to assume load from two nodes. The other node > (ie the one not mentioned in the "to assume load from" message) does > have the Anticompacting messages I'd been expecting. > > The log reads: > DEBUG 19:41:12,464 Beginning bootstrap process > DEBUG 19:41:12,479 Added /10.240.74.208/PostingData as a > bootstrap source > DEBUG 19:41:12,480 Requesting from /10.240.74.208 ranges > (26387927685172847128195341375882448808,3827402348864769685218 > 9267330197674758] > DEBUG 19:41:12,481 Requesting from /10.240.74.208 ranges > (26387927685172847128195341375882448808,3827402348864769685218 > 9267330197674758] > DEBUG 19:41:12,483 Added /10.214.118.143/PostingData as a > bootstrap source > DEBUG 19:41:12,483 Requesting from /10.214.118.143 ranges > (38274023488647696852189267330197674758,9854626435259012793337 > 6074587615077134] > DEBUG 19:41:12,483 Requesting from /10.214.118.143 ranges > (38274023488647696852189267330197674758,9854626435259012793337 > 6074587615077134] > DEBUG 19:41:12,484 attempting to connect to /10.240.74.208 > DEBUG 19:41:12,505 attempting to connect to /10.214.118.143 > > Thanks, > Aaron Lav (a...@pobox.com) > > > >
