Thank you Stefano. I have problems to understand the implementation of a sequential repair.
In the doc of datastax <https://docs.datastax.com/en/cassandra/2.1/cassandra/operations/opsRepairNodesManualRepair.html>they explain that in a sequential repair "The coordinator node constructs the Merkle trees for one replica after the other". But in the logs I can see this lines INFO [AntiEntropyStage:1] 2016-06-24 10:02:09,000 RepairSession.java:171 - [repair #f31281c0-39e1-11e6-96a9-d559db24120b] Received merkle tree for syndic_mail_unsub from /192.0.0.2 For every replica. Then is it the coordinator how construct the merkle tree demanding that to every replica? Why with repair sequential are we having more stream of sstable? Are they sharing the whole snapshot? Thnak you again <https://docs.datastax.com/en/cassandra/2.1/cassandra/operations/opsRepairNodesManualRepair.html> Saludos Jean Carlo "The best way to predict the future is to invent it" Alan Kay On Thu, Jun 23, 2016 at 5:34 PM, Stefano Ortolani <ostef...@gmail.com> wrote: > Yes, because you keep a snapshot in the meanwhile if I remember correctly. > > Regards, > Stefano > > On Thu, Jun 23, 2016 at 4:22 PM, Jean Carlo <jean.jeancar...@gmail.com> > wrote: > >> Cassandra 2.1.12 >> >> In the moment of a repair -pr sequential, we are experimenting an >> exponential increase of number of sstables. For a table lcs. >> >> If someone of you guys kowns if theoritically speaking a sequential >> repair doing more sstable streaming among replicas than a parallel repair? >> >> >> >> Best regards >> >> Jean Carlo >> >> "The best way to predict the future is to invent it" Alan Kay >> > >
