The parent repair session will be on the node that you kicked off the
repair on. Are the logs above from that node? Can you make it a bit clearer
how many nodes are involved and the corresponding logs from each node?
On 9 January 2018 at 09:49, Hannu Kröger wrote:
> We have
We have run restarts on the cluster and that doesn’t seem to help at all.
We ran repair separately for each table that seems to go through usually but
running a repair on a keyspace doesn’t.
Anything anyone?
Hannu
> On 3 Jan 2018, at 23:24, Hannu Kröger wrote:
>
> I can
I can certainly try that. No problem there.
However wouldn’t we then get this kind of errors if that was the case:
java.lang.RuntimeException: Cannot start multiple repair sessions over the same
sstables
?
Hannu
> On 3 Jan 2018, at 20:50, Nandakishore Tokala
>
hi Hannu,
I think some of the repairs are hanging there. please restart all the nodes
in the cluster and start the repair
Thanks
Nanda
On Wed, Jan 3, 2018 at 9:35 AM, Hannu Kröger wrote:
> Additional notes:
>
> 1) If I run the repair just on those tables, it works fine
>
Additional notes:
1) If I run the repair just on those tables, it works fine
2) Those tables are empty
Hannu
> On 3 Jan 2018, at 18:23, Hannu Kröger wrote:
>
> Hello,
>
> Situation is as follows:
>
> Repair was started on node X on this keyspace with —full —pr. Repair
Hello,
Situation is as follows:
Repair was started on node X on this keyspace with —full —pr. Repair fails on
node Y.
Node Y has debug logging on (DEBUG on org.apache.cassandra) and I’m looking at
the debug.log. I see following messages related to this repair request:
---
DEBUG