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
restarti
On Tue, May 12, 2015 at 9:59 AM, arun sirimalla wrote:
> Try running repair on node 3.
>
Mostly disagree. If a node is empty after a bootstrap, remove it and
re-bootstrap it.
=Rob
Analia,
Try running repair on node 3.
On Tue, May 12, 2015 at 7:39 AM, Analia Lorenzatto <
analialorenza...@gmail.com> wrote:
> Hello guys,
>
>
> I have a cluster 2.1.0-2 comprised of 3 nodes. The replication factor=2.
> We successfully added the third node last week. After that, We ran clean
Hello guys,
I have a cluster 2.1.0-2 comprised of 3 nodes. The replication factor=2.
We successfully added the third node last week. After that, We ran clean
ups on one node at that time. Then we ran repairs on all the nodes, and
finally compactions on all the CFs.
Last night, I noticed the c
