apache / apache/rocketmq-connect
Fix OFFSET_ILLEGAL error when RmqSourceTask pulls messages
Open
- Dominant language
- Java
- Stars
- 141
- Forks
- 120
- PR merge metrics
- No merged PRs in 30d
Description
When the RmqSourceTask pull message returns OFFSET_ILLEGAL, the pull of the message is blocked
Contributor guide
Research direction
Start by locating RmqSourceTask and tracing how its message-pull result is handled when the broker returns OFFSET_ILLEGAL. Reproduce the blocked pull if possible, then inspect any existing tests around RmqSourceTask; done means OFFSET_ILLEGAL no longer blocks subsequent message pulls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100