Get wrong offset record when restart connect service after increase the partition number from 1 to 3. [DBZ-1551]
Open
component/container-images
component/core-library
component/mysql-connector
migrated-from-jira
type/bug
- Dominant language
- HTML
- Stars
- 6
- Forks
- 8
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 1
Description
Migrated from [DBZ-1551](https://issues.redhat.com/browse/DBZ-1551)
After running for a while that offset topic only had 1 partition.
Increase partition number to 3, then, some connector store theirs offset to partition 1 or partition 2.
All connector will get offset recored from partition 0 when restart all container.
Contributor guide
Research direction
Reproduce the reported sequence: run with one offset-topic partition, increase it to three, let connectors store offsets, then restart all containers. Inspect how connectors select offset records during restart; done means each connector resumes from its own stored offset rather than partition 0. No files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100