You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: