eventservice: scan window can strand transaction cursor
Open
@asddongmen is already working on this.
Since Aug 19, 2026.
affects-8.5
severity/minor
type/bug
- Dominant language
- Go
- Stars
- 56
- Forks
- 63
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 34
Description
When an interrupted event-service scan publishes a transaction cursor (C, S, nil), the adaptive scan window can later shrink below C. eventBroker then produces an empty range with CommitTsEnd < CommitTsStart, skips the scan, and retains the non-zero cursor. Signal resolved-ts is also suppressed, so the dispatcher can remain stuck.
Expected behavior: normalize the effective range to [C, C] and let EventStore resume after transaction start-ts S for other transactions sharing commit-ts C. This was reproduced while testing the staged redo ACK changes in #5956.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.