Wouldn't it be a better idea to issue removenode on the crashed node, wipe
the whole data directory (including system) and let it bootstrap cleanly so
that it's not part of the cluster while it gets back up to speed?
On Tue, Nov 11, 2014, 12:32 PM Robert Coli rc...@eventbrite.com wrote:
On Tue,
On Wed, Nov 12, 2014 at 6:50 AM, Eric Stevens migh...@gmail.com wrote:
Wouldn't it be a better idea to issue removenode on the crashed node, wipe
the whole data directory (including system) and let it bootstrap cleanly so
that it's not part of the cluster while it gets back up to
Yes, with
Hi Eric,
The data are stored in JBOD. Only one of the disk got crashed other 3 disk
still holds the old data . That's why I didn't clean the whole node and issue a
fresh restart
Thanks Rob. Will do try that way.
From: Eric Stevens
Sent: Wednesday, November 12, 2014 8:21 PM
I was able to complete the repair, repairing one keyspace and cf each time.
However the last session is still shown as an active process, even if
the session has been successfully completed, this is the log:
INFO [CompactionExecutor:252] 2014-01-14 03:10:13,105
CompactionTask.java (line 275)
Hi,
I have two nodes with Cassandra 2.0.3, where repair sessions hang for an
undefinite time. I'm running nodetool repair once a week on every node,
on different days. Currently I have like 4 repair sessions running on
each node, one since 3 weeks and none has finished.
Reading the logs I
On Wed, Jan 8, 2014 at 8:52 AM, Paolo Crosato paolo.cros...@targaubiest.com
wrote:
I have two nodes with Cassandra 2.0.3, where repair sessions hang for an
undefinite time. I'm running nodetool repair once a week on every node, on
different days. Currently I have like 4 repair sessions
Hi,
Can you attach the logs around repair. Please do that for node which
triggered it and nodes involved in repair. I will try to find something
useful.
Thanks,
Sankalp
On Wed, Jan 8, 2014 at 10:18 AM, Robert Coli rc...@eventbrite.com wrote:
On Wed, Jan 8, 2014 at 8:52 AM, Paolo Crosato
