krishvishal opened a new issue, #3793:
URL: https://github.com/apache/iggy/issues/3793
### Bug description
## Summary
`PurgeTopic` mutates partition state out of band (metadata op → reconciler
→ pump) and never
touches the partition journal. Superseded ops stay repairable. After a
node restart, partition
journal repair replays them and undoes the purge.
The partition plane has no checkpoint, so there is no repair floor a purge
can advance.
## Repro
```
cargo nextest run --features vsr --retries 0 \
-E 'test(/should_purge_topic_and_clear_consumer_offsets.*restart_on/)'
```
~30% fail. Control: `restart_off` 24/24 pass. Three sites fire depending
on interleaving:
| site | assertion | observed |
|---|---|---|
| `purge_delete_scenario.rs:992` | consumer offset cleared | offset
returns |
| `purge_delete_scenario.rs:1006` | group offset cleared | offset returns |
| `purge_delete_scenario.rs:1331` | single segment at offset 0 | `[0, 5,
10]`, `[0, 5, 10, 15]` |
## Evidence
Restarted node:
```
.412599 purge-partition reset partition to empty shard=1 generation=1
.429027 repair prepare received shard=1 op=1
... ops 2..26
.519273 partition journal repair complete through_op=26
(commit_min_before=0)
```
Peer: `.428320 served partition repair range from_op=1 to_op=26
served_through=26`
### Affected area / component
_No response_
### Deployment
None
### Versions
_No response_
### Hardware / environment
_No response_
### Sample code
_No response_
### Logs
_No response_
### Iggy server config
_No response_
### Reproduction
_No response_
### 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
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
