Replica recovery panics with “repair range must be non-empty” after requesting 9..=8

Open
#4,230 2 comments 0 reactions 1 assignee View on GitHub

@Reasonable-Solutions is already working on this.

Since Sep 19, 2026.

Assessment

This issue has not been assessed yet.

Description

bug cluster
Bug description

I was running a soak over from our other pipelines and ran into some issues after doing a leader restart (part of the soak).

Repro and fix https://github.com/Reasonable-Solutions/iggy-repro
maybe related to #4073?

Affected area / component

Clustering / replication

Deployment

Compiled from source

Versions

362bd78295fc5df085e8410c77fe2ff29c71256b

Hardware / environment

A pile of HP z2 workstaions, some 20 core intel cpu, 64gb ram, 4tb nvme per node.

Sample code

see the repro in the issue

Logs

No response

Iggy server config

No response

Reproduction

see the repro

Contribution
  • I'm willing to submit a pull request to fix this bug
Good first issue
  • I think this could be a good first issue for a new contributor
Dominant language
Rust
Stars
4.9k
Forks
442
Avg merge
2d 23m
Merged PRs (30d)
153

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/iggy

All issues in apache/iggy

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.