017 um 10:04
An: "user@cassandra.apache.org" <user@cassandra.apache.org>
Betreff: Re: Node crashes on repair (Cassandra 3.11.1)
Hi Jeff,
the repairs worked fine before on version 3.9. I noticed that the validation
tasks when doing a repair are not bound anymore to the concurrent_com
<jji...@gmail.com>
Antworten an: "user@cassandra.apache.org" <user@cassandra.apache.org>
Datum: Donnerstag, 30. November 2017 um 19:46
An: cassandra <user@cassandra.apache.org>
Betreff: Re: Node crashes on repair (Cassandra 3.11.1)
That was worded poorly. The depth has
That was worded poorly. The depth has a max depth of 20, the tree is the
same size for any range > 2**20.
On Thu, Nov 30, 2017 at 10:43 AM, Jeff Jirsa wrote:
> Merkle trees have a fixed size/depth (2**20), so it’s not that, but it
> could be timing out elsewhere (or still
Merkle trees have a fixed size/depth (2**20), so it’s not that, but it could be
timing out elsewhere (or still running validation or something)
--
Jeff Jirsa
> On Nov 30, 2017, at 10:12 AM, Javier Canillas
> wrote:
>
> Christian,
>
> I'm not an expert, but maybe
Christian,
I'm not an expert, but maybe the merkle tree is too big to transfer between
nodes and that's why it times out. How many nodes do you have and what's
the size of the keyspace? Have you ever done a successfully repair before?
Cassandra reaper does repair based on tokenrange (or even
Hello,
after updating our cluster to Cassandra 3.11.1 (previously 3.9) running a
‘nodetool repair –full’ leads to the node crashing.
Logfile showed the following Exception:
ERROR [ReadRepairStage:36] 2017-11-30 07:42:06,439 CassandraDaemon.java:228 -
Exception in thread