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

Segment count for incremental repairs remains 1 per node regardless of the segment count specified (3.2.0 + ) #1502

Open
Valgar opened this issue May 1, 2024 · 1 comment
Assignees
Labels

Comments

@Valgar
Copy link

Valgar commented May 1, 2024

Project board link

When specifying segment count for incremental repairs in repair, the value seems to be ignored (including any defaults set in config)

Unsure if this is expected behaviour, as segment count/node can be specified for full repairs.

This causes failures and backoffs during incrementals on large segments.

Screenshots of launching incremental repair and specifying segment count/node and the resulting segment count of the running repair (3 node cluster 1 per node only, instead of 64 per node)

reaper3 2 0-incremental-repair-config reaper3 2 0-incremental-repair-running
@adejanovski adejanovski self-assigned this Jun 18, 2024
@adejanovski
Copy link
Contributor

We will introduce a new "Subrange incremental" type of repair to cover this case.
I think there are cases where a global incremental will work better than the subrange version, and vice versa.

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

No branches or pull requests

2 participants