On Sun, Nov 7, 2010 at 11:58 PM, Reverend Chip wrote:
> Is there an existing tool to just read everything from every node, just
> to force a read repair on everything?
>
"nodetool repair", of course. me-- for getting FAQ and mailing list out of
order.
On 11/6/2010 8:26 PM, Jonathan Ellis wrote:
> On Sat, Nov 6, 2010 at 4:51 PM, Reverend Chip wrote:
>> Am I to understand that
>> ring maintenance requests can just fail when partially complete, in the
>> same manner as a regular insert might fail, perhaps due to inter-node
>> RPC overflow?
> Yes,
On Sat, Nov 6, 2010 at 4:51 PM, Reverend Chip wrote:
> On 11/6/2010 1:48 PM, Jonathan Ellis wrote:
>> Did any of the nodes log any dropped messages?
>
> I didn't keep timestamps of the maintenance steps, so I will be unable
> to be sure which log entries correspond to which failure states. I di
On 11/6/2010 1:48 PM, Jonathan Ellis wrote:
> On Fri, Nov 5, 2010 at 8:03 PM, Chip Salzenberg wrote:
>> In the below "nodetool ring" output, machine 18 was told to loadbalance over
>> an hour ago. It won't actually leave the ring. When I first told it to
>> loadbalance, the cluster was under hea
On Fri, Nov 5, 2010 at 8:03 PM, Chip Salzenberg wrote:
> In the below "nodetool ring" output, machine 18 was told to loadbalance over
> an hour ago. It won't actually leave the ring. When I first told it to
> loadbalance, the cluster was under heavy write load; I've turned off the
> write load,
In the below "nodetool ring" output, machine 18 was told to loadbalance over
an hour ago. It won't actually leave the ring. When I first told it to
loadbalance, the cluster was under heavy write load; I've turned off the
write load, but the node won't actually leave, still. Help?
(It also colle
