Daniel

Results 22 comments of Daniel

where can this jar be found? in my environment it does not exist epkdaek@elx721027t9:~/cassandra/ecchronos-binary-5.0.1-SNAPSHOT$ pwd /home/epkdaek/cassandra/ecchronos-binary-5.0.1-SNAPSHOT epkdaek@elx721027t9:~/cassandra/ecchronos-binary-5.0.1-SNAPSHOT$ find . -name ec*.jar epkdaek@elx721027t9:~/cassandra/ecchronos-binary-5.0.1-SNAPSHOT$ epkdaek@elx721027t9:~/cassandra/ecchronos-binary-5.0.1-SNAPSHOT$ ls lib/e* lib/ecchronos-binary-5.0.1-SNAPSHOT.pom lib/error_prone_annotations-2.18.0.jar epkdaek@elx721027t9:~/cassandra/ecchronos-binary-5.0.1-SNAPSHOT$

should the restart suggested to trigger the scenario be the same as if ecc is started via ./bin/ecctool start -f and the stopping it via ctrl-C and then starting it...

After discussion with the author this is how to reproduce the issue/bug. run "ecctool schedules" and notice "completed at" and "next repair" epkdaek@elx721027t9:~/cassandra/ecchronos-binary-5.0.0-SNAPSHOT$ ./bin/ecctool schedules Snapshot as of 2024-02-26 10:48:55...

The repair jobs seems to execute just fine. I have changed the repair schedule to 10 min in ecc.yml before starting. epkdaek@elx721027t9:~/cassandra/ecchronos-binary-5.0.0-SNAPSHOT$ ./bin/ecctool start -f ecc started with pid 1066218...

> > Since ecchronos always assumes a repair is successful if the history is empty, I don't see why this would be considered a bug if ecchronos is crashed/restarted before...

#2 is almost how it is done today. just that it recalculates if it is restarted again. Who can decide between #1 and #2 orif there are more?

The working assumption that was decided is that when a new table is found ecchronos should update the histroy that a repair has been done now without doing the repair...

There are a few times debug is LOGed. Which should be kept and/or changed to info? A DoD needs to be defined for this issue epkdaek@elx721027t9:~/github/ecchronos$ git grep "LOG.debug" application/src/main/java/com/ericsson/bss/cassandra/ecchronos/application/ECChronosInternals.java:...

This is the suggestion epkdaek@elx721027t9:~/github/ecchronos$ git grep "LOG.debug" INFO: application/src/main/java/com/ericsson/bss/cassandra/ecchronos/application/ECChronosInternals.java: LOG.debug("Table {} last repaired at {}", tableReference, lastRepairedAt); INFO: application/src/main/java/com/ericsson/bss/cassandra/ecchronos/application/ECChronosInternals.java: LOG.debug("Table {} remaining repair time {}", tableReference, remainingRepairTime); INFO: application/src/main/java/com/ericsson/bss/cassandra/ecchronos/application/config/ConfigRefresher.java:...

Some might vene be changed to error? LOG.debug("Unable to connect over JMX", e); and LOG.debug("Unable to connect over CQL", e); sound like an error to me