So we tried decommissionning the 100.5 node, then re added it to the ring.
It now appears to be streaming data properly to that node.
On Tue, Sep 13, 2011 at 6:56 AM, David McNelis
wrote:
> I ran a repair on 100.5. It returned back almost immediately and netstats
> and tpstats don't show any
I ran a repair on 100.5. It returned back almost immediately and netstats
and tpstats don't show any additional activity. Nor does the Java process
start using more juice.
When I look at the cfstats for the main keyspace, number of keys is 0 in all
cases. When I look at other nodes in the clust
Try a reapir on 100.5 , it will then request the data from the existing nodes.
You will then need to clean on the existing three nodes once the repair has
completed.
Cheers
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 13/09/2011, a
Auto-bootstrapping is turned on and the node had been started several hours
ago. Since the node already shows up as part of the ring I would imagine
that nodetool join wouldn't do anything.Is there a command to jumpstart
bootstrapping?
On Mon, Sep 12, 2011 at 4:22 PM, Jonathan Ellis wrote:
Looks kind of like the 4th node was added to the cluster w/o bootstrapping.
On Mon, Sep 12, 2011 at 3:59 PM, David McNelis
wrote:
> We are running the datastax .8 rpm distro. We have a situation where we
> have 4 nodes and each owns 25% of the keys. However the last node in the
> ring does not
We are running the datastax .8 rpm distro. We have a situation where we
have 4 nodes and each owns 25% of the keys. However the last node in the
ring does not seem to be getting much of a load at all.
We are using the random partitioner, we have a total of about 20k keys that
are sequential...
