Just in case I want to clarify that after bootstrapping the third node, it
got data and seemed to be working fine. But it was the last night when
the cluster started behaving in a weird way. The last node (successfully
added last week) were being reported up and down all the time. After
restarting cassandra service, the node got empty but reported as Up and
Normal.
Also, the amount of data reported by nodetool on the other nodes is much
more than the amount already used in the device, is that normal?
root@10.0.0.a:~# df -h /mnt
Filesystem Size Used Avail Use% Mounted on
/dev/xvdb1 745G 163G 583G 22% /mnt/cassandra
root@:10.0.0.b~$ df -h /mnt
Filesystem Size Used Avail Use% Mounted on
/dev/xvdb1 745G 196G 550G 27% /mnt/cassandra
# nodetool status
Datacenter: us-east
===================
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
-- Address Load Tokens Owns (effective) Host ID
Rack
UN 10.0.0.a 391.34 GB 256 66.7%
eed9e9f5-f279-4b2f-b521-c056cbf65b52 1c
UN 10.0.0.b 383.38 GB 256 68.3%
19492c26-4458-4a0b-af04-72e0aab6598e 1c
Thanks in advance!
On Tue, May 12, 2015 at 2:35 PM, Robert Coli <rc...@eventbrite.com> wrote:
> On Tue, May 12, 2015 at 9:59 AM, arun sirimalla <arunsi...@gmail.com>
> wrote:
>
>> Try running repair on node 3.
>>
>
> Mostly disagree. If a node is empty after a bootstrap, remove it and
> re-bootstrap it.
>
> =Rob
>
>
--
Saludos / Regards.
Analía Lorenzatto.
“It's possible to commit no errors and still lose. That is not weakness.
That is life". By Captain Jean-Luc Picard.
