On 30 May 2017, at 21:11, Varun Gupta wrote:
I am missing the point, why do you want to re-trigger the process post
repair. Repair will sync the data correctly.
Sorry - I mis-represented that. I want to trigger something else, not
repair.
I am investigating a CQRS/Event Sourced pattern which C* as a
distributed event log and a process reading from that log, changing
state in other data bases (Solr, Graph-DB, other C* tables, etc.)
Since I do not want to write to/read from the commit log with
EACH_QUORUM or LOCAL_QUORUM it could happen that the process processing
the event log misses an event that only later pops up during repair.
What that happens, I'd like to re-process the log (my processing is
idempotent, so it can just go again).
This is why I was looking for a way to learn that a repair has actually
repaired something.
Jan
On Mon, May 29, 2017 at 8:07 AM, Jan Algermissen
<algermissen1...@icloud.com
wrote:
Hi,
is it possible to extract from repair logs the writetime of the
writes
that needed to be repaired?
I have some processes I would like to re-trigger from a time point if
repair found problems.
Is that useful? Possible?
Jan
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org
