Comments (3)
rkozlo
commented on September 27, 2024
One maybe usefule info. In cassandra-reaper logs infos about this segment only at time when it started. After that not even one occurence
from cassandra-reaper.
lapo-luchini
commented on September 27, 2024
Same here, I often have segments older than the 120 minutes that I have configured as timeout.
from cassandra-reaper.
pedro-gordo
commented on September 27, 2024
I might have hit a bug related to this. We're running 3.2. I had a repair that was not getting completed even though there was only one segment left to go. Even though there were no pending compactions, and the nodes had a lot of headroom, there were always two of these messages:
Attempting to run new segment...
All nodes are busy or have too many pending compactions for the remaining candidate segments.
All nodes are busy or have too many pending compactions for the remaining candidate segments.
Repair amount done 179.0
After aborting the segment, pausing the repair, and then re-activating it, I noticed the following error on the log:
ERROR [2023-05-18 14:45:53,642] [<CLUSTER NAME>:<CLUSTER UUID>] i.c.s.RepairRunner - RepairRun FAILURE, scheduling retry
java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0
at java.base/jdk.internal.util.Preconditions.outOfBounds(Unknown Source)
at java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Unknown Source)
at java.base/jdk.internal.util.Preconditions.checkIndex(Unknown Source)
at java.base/java.util.Objects.checkIndex(Unknown Source)
at java.base/java.util.ArrayList.get(Unknown Source)
at io.cassandrareaper.service.RepairRunner.isAllowedToRun(RepairRunner.java:267)
at io.cassandrareaper.service.RepairRunner.run(RepairRunner.java:234)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:125)
at com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:57)
at com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:78)
at com.codahale.metrics.InstrumentedScheduledExecutorService$InstrumentedRunnable.run(InstrumentedScheduledExecutorService.java:241)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at com.codahale.metrics.InstrumentedThreadFactory$InstrumentedRunnable.run(InstrumentedThreadFactory.java:66)
at java.base/java.lang.Thread.run(Unknown Source)
from cassandra-reaper.
Related Issues (20)
- Builds are broken due to a missing ruby dependency
- Typo/spelling issues
- web UI can not login when Authentication is activate HOT 3
- API REST repair_run segmentCountPerNode HOT 2
- (Re-)Deployment fails with "com.datastax.driver.core.exceptions.AlreadyExistsException: Table reaper_db.running_repairs already exists" exception HOT 5
- Fix testSSLHotReload so it can be run locally
- Change Request: Build RPM Packages with SHA256 digests enabled.
- Failed creating a merkle tree for [repair #c0c157f0-e14a-11ee-b320-bdc4e5fd08de on reaper_current/running_repairs, [(-8896895687978311387,-8888847627918162438], (-881535601694419919,-867088063190097011], (1356177826732174702,1357186491253880239], (6263469266031338450,6279809997892748801]]], /<IP>:7000 HOT 3
- Add an option to persist the memory storage data using a local store
- setting `blacklistTwcsTables: false` does not include twcs tables in subsequent runs HOT 3
- Add env variable to Docker image for Memory Storage backend location
- Support Keystore configuration for communicating with multiple Management API deployments HOT 1
- Fix High/Critical CVEs
- Fix Snakeyaml CVEs
- Fix Guava CVEs
- Fix Docker image library CVEs
- Can we have count of segments failed as part of prometheusmetrics
- Segment count for incremental repairs remains 1 per node regardless of the segment count specified (3.2.0 + ) HOT 1
- Issues running the container with a read only root FS
- Cassandra Reaper 3.6.0 - Noticed bug(tombstone issue) & downgraded to 3.2.0
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cassandra-reaper.