As part of my continuous abuse of a small cluster for Chef cookbook
development, I've run across a strange issue I'm hoping someone can
explain. The following is output after upgrading from beta2 to beta3
and running nodetool rebalance on .140.224:
Address Status Load Range
Ring
HS3ltoTahEIsK65e
10.177.144.176Up 5.41 KB B61cmDQkiI92SoCu
|<--|
10.177.140.224Up 2.33 KB Bootstrap
| |
10.177.138.136Up 6.13 KB HS3ltoTahEIsK65e
|-->|
>From the logs:
INFO [STREAM-STAGE:1] 2010-03-22 03:16:28,586 StreamOut.java (line
66) Sending a stream initiate message to /10.177.138.136 ...
INFO [RMI TCP Connection(6)-173.203.205.232] 2010-03-22 03:16:30,596
StorageLoadBalancer.java (line 365) Sleeping 90000 ms to wait for load
information...
INFO [RMI TCP Connection(6)-173.203.205.232] 2010-03-22 03:18:00,616
BootStrapper.java (line 104) New token will be Bootstrap to assume
load from /10.177.138.136
INFO [RMI TCP Connection(6)-173.203.205.232] 2010-03-22 03:18:00,616
StorageService.java (line 1430) re-bootstrapping to new token
Bootstrap
INFO [RMI TCP Connection(6)-173.203.205.232] 2010-03-22 03:18:00,616
StorageService.java (line 376) Joining: sleeping 30000 for pending
range setup
INFO [RMI TCP Connection(6)-173.203.205.232] 2010-03-22 03:18:30,626
StorageService.java (line 376) Bootstrapping
INFO [MESSAGE-DESERIALIZER-POOL:1] 2010-03-22 03:18:30,656
StorageService.java (line 180) Bootstrap/move completed! Now serving
reads.
Although it is possible the range 'Bootstrap' was randomly generated,
it seems more likely it has somehow been assigned explicitly. Can
someone illuminate what is going on here?
b
