ydb-platform / ydb-platform/ydb-java-sdk
Topic API control event ordering
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 53
- Forks
- 40
- Avg merge
- 9h 51m
- Merged PRs (30d)
- 7
Description
Problem
The Topic API client currently receives StartPartitionSessionEvent and StopPartitionSessionEvent events from AsyncReader without ordering guarantees. This leads to race conditions where a stop event may be processed before its corresponding start event, causing undefined behavior.
Expected Behavior
The Topic API should guarantee strict event ordering, ensuring that each control event is delivered to the client only after the previous event has been fully processed
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.
Research direction
Start with the Topic API client and AsyncReader handling of StartPartitionSessionEvent and StopPartitionSessionEvent. Trace how control events are delivered, then verify that each event reaches the client only after the previous event has been fully processed, with stop events never preceding their corresponding start events.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100