Skip to content
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

All nodes are busy or have too many pending compactions for the remaining candidate segments: Cassandra-Reaper 3.6.1 #1514

Open
Hip3007 opened this issue Aug 5, 2024 · 1 comment

Comments

@Hip3007
Copy link

Hip3007 commented Aug 5, 2024

Project board link

Dear all,

743 / 5,000
We are facing a rather difficult problem when repairing with reaper:
We have installed the latest reaper version 3.6.1.
We tried running repair with the options DC_Aware or Sequential. Both of these options are tested with parallel from low to high.
But we still get an error with the log: All nodes are busy or have too many pending compactions for the remaining candidate segments.
We check on nodes that have almost no compaction or repair running or very little running.
We repaired the nodes manually and there were no errors, nor were the nodes overloaded.
We're suspicious because of the reaper itself and we haven't found the problem yet.
Please help us see where to find problems and how to handle them?
Thanks a lot.

┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: REAP-5

@Hip3007
Copy link
Author

Hip3007 commented Aug 6, 2024

Any one help me !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant