Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
When running repair for the same keyspace - prometheusMetrics are not updated
See original GitHub issueI have scheduled repairs on multile keyspaces to run every week.
The first run of every keyspace can be montored via /prometheusMetrics (grafana), but when the run finishes and a new schedule takes place, the metrics shows the previous run => io_cassandrareaper_service_RepairRunner_repairProgress=1.
When I restart cassandra-reaper container the /prometheusMetrics picks up the new runs.
I’ve tried to run version 2.2.4 and also master of cassandra-reaper.
Any tips, how to resolve this issue?
┆Issue is synchronized with this Jira Task by Unito ┆Issue Number: K8SSAND-200
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
It will be in 3.0 actually, which will be released within a few days. Current
masteris considered as working… until bugs are found 😃 Right now it should be in a solid state as we approach release time. You do not need to build it yourself as it is built automatically for each push to themasterbranch. You can find beta packages here, and can use themastertag of the docker image.Yes, the functionality works as expected.
Many thanks.