Hi,

 

I am new to Cassandra and I would like to hear your thoughts on this. 

We are running our tests with Cassandra 1.2.1, in relatively small dataset
~60GB.

Nodetool repair command has been running for almost 24hours and I can't see
any activity from the logs or JMX.

What am I missing? Or there is a problem with node tool repair?

What other commands that I can run to do a sanity check on the cluster?

Can I run nodetool repair on different node in the same time?

 

 

Here is the current test deployment of Cassandra

$ nodetool status

Datacenter: ams01 (Replication Factor 2)

=================

Status=Up/Down

|/ State=Normal/Leaving/Joining/Moving

--  Address           Load       Tokens  Owns   Host ID
Rack

UN  10.70.48.23       38.38 GB   256     19.0%
7c5fdfad-63c6-4f37-bb9f-a66271aa3423  RAC1

UN  10.70.6.78        58.13 GB   256     18.3%
94e7f48f-d902-4d4a-9b87-81ccd6aa9e65  RAC1

UN  10.70.47.126      53.89 GB   256     19.4%
f36f1f8c-1956-4850-8040-b58273277d83  RAC1

Datacenter: wdc01 (Replication Factor 1)

=================

Status=Up/Down

|/ State=Normal/Leaving/Joining/Moving

--  Address           Load       Tokens  Owns   Host ID
Rack

UN  10.24.116.66      65.81 GB   256     22.1%
f9dba004-8c3d-4670-94a0-d301a9b775a8  RAC1

Datacenter: sjc01 (Replication Factor 1)

=================

Status=Up/Down

|/ State=Normal/Leaving/Joining/Moving

--  Address           Load       Tokens  Owns   Host ID
Rack

UN  10.55.104.90      63.31 GB   256     21.2%
4746f1bd-85e1-4071-ae5e-9c5baac79469  RAC1

 

 

Many Thanks,

 

Haithem

 

Reply via email to