-
Notifications
You must be signed in to change notification settings - Fork 217
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
if endTime is set, so must startTime be set #281
Comments
@adisharoon would you be interested in uploading your logs (and even a cql export of the reaper_db keyspace)? if you're unsure about privacy concerns you could email it directly to me on mick@thelastpickle.com |
@adisharoon : I created a snapshot release to issue a quick fix >> https://github.com/thelastpickle/cassandra-reaper/releases/tag/1.0.1-SNAPSHOT Please tell us how it works, and we'd gladly take the logs as @michaelsembwever to try and understand how this could have happened. Thanks ! |
move the setting of the startTime to when the segment is triggered, as this is definite, rather than the jmx notification recieved afterwards that the segment has started (as we don't always get it).
1.0.1 SNAPSHOT allows repairs to continue, but does log warnings followed by an exception.
|
I will fix that @clangaxon In fact it should already be fixed in The problem with removing the preconditions is that it just moves the error to other places in the code, as the IllegalArgumentException above shows. |
Fixed in #282 Expect the 1.0.1 release with 24 hrs. |
Thanks! |
The problem should be fixed in 1.0.1-SNAPSHOT @clangaxon @adisharoon : any chance you could test this release and tell us if the fix works for you? We'll then release a final 1.0.1. Thanks |
So far, it appears to be functioning properly and has stopped all the warnings and errors. |
thanks for the feedback @clangaxon. Closing the issue. |
I am unfortunately seeing this issue even after upgrading to 1.0.1. I am running one Reaper per DC and the "endTime is set, so must startTime be set" error is happening occasionally (I'd say less frequently than prior to upgrading to 1.0.1). please see attached log files: data causing the issue (you can see they come from dc2 log file):
everything goes back to normal when I fix the data by running:
|
@ludekdolejsky , i'll look into this. but i'll need more logs than what you provided. all logs since that particular repair started would be best. also it needs to be opened as a new ticket, as this failure message is only a symptom to various underlying causes that need to be addressed separately… (and hopefully most of those causes have been fixed already). but this can be done when more info is provided. |
@michaelsembwever I have opened #291 with full logs. Hope it helps. Thanks, Ludek |
For some of our cassandra reaper instances, the web UI has stopped displaying running repairs, and the javascript console shows 500 errors. The only clue I've found is the following exception which occurs frequently in the log. This is for the new version 1.0.0
The text was updated successfully, but these errors were encountered: