Thanks for the note.
Can you help me with something else? I can’t seem to get any data to transfer during bootstrapping...I must be doing something wrong.
Here is what I did: I took 0.6.0-beta2, loaded 2 machines with 60-70GB each. Then I started a third node, with AutoBootstrap true. The node claims it is bootstrapping:
INFO - Auto DiskAccessMode determined to be mmap
INFO - Saved Token not found. Using Rb0mePN3PheW3haA
INFO - Creating new commitlog segment /home/cooperb/cassandra/commitlog/CommitLog-1267594407761.log
INFO - Starting up server gossip
INFO - Joining: getting load information
INFO - Sleeping 90000 ms to wait for load information...
INFO - Node /22.214.171.124 is now part of the cluster
INFO - Node /126.96.36.199 is now part of the cluster
INFO - InetAddress /188.8.131.52 is now UP
INFO - InetAddress /184.108.40.206 is now UP
INFO - Joining: getting bootstrap token
INFO - New token will be user148315419 to assume load from /220.127.116.11
INFO - Joining: sleeping 30000 for pending range setup
INFO - Bootstrapping
But when I run nodetool streams, no streams are transferring:
Not sending any streams.
Not receiving any streams.
And it doesn’t look like the node is getting any data. Any ideas?
Thanks for the help...
On 3/2/10 12:22 PM, "Jonathan Ellis" <firstname.lastname@example.org> wrote:
On Tue, Mar 2, 2010 at 1:54 PM, Brian Frank Cooper
> Hi folks,
> I’m running 0.5 and I had 2 nodes up and running, then added a 3rd node in
> bootstrap mode. I understand from other discussion list threads that the new
> node doesn’t serve reads while it is bootstrapping, but does that mean it
> won’t connect at all?
it doesn't start the thrift listener until it is bootstrapped, so yes.
(you can tell when it's bootstrapped by when it appears in nodeprobe
ring. 0.6 also adds bootstrap progress reporting via jmx.)
> When I try to connect from my java client, or
> cassandra-cli, I get the exception below. Is it the expected behavior?
> (Also, cassandra-cli says “Connected to xxx.yahoo.com” even though it isn’t
> really connected...)
This is fixed in https://issues.apache.org/jira/browse/CASSANDRA-807
for 0.6, fwiw.
Principal Research Scientist