Uploaded image for project: 'Debezium'
  1. Debezium
  2. DBZ-1551

Get wrong offset record when restart connect service after increase the partition number from 1 to 3.

XMLWordPrintable

    • Hide

      1. Cluster mode, tow node (container);
      2. Offset topic only have 1 partition;
      3. Create multi mysql connector; (at least 3)
      4. Change data, all connector have offset recored in partition 0.
      4. Increate offset topic partition number to 3. (at least 3)
      5. Change data, and some connector store their offset recored to partition 1 or partition 2.
      6. Restart all connect container, all connector read offset from partition 0.
      7. Then, repeat data in some connector topic (stored offset to partition 1 or partition 2).

      Show
      1. Cluster mode, tow node (container); 2. Offset topic only have 1 partition; 3. Create multi mysql connector; (at least 3) 4. Change data, all connector have offset recored in partition 0. 4. Increate offset topic partition number to 3. (at least 3) 5. Change data, and some connector store their offset recored to partition 1 or partition 2. 6. Restart all connect container, all connector read offset from partition 0. 7. Then, repeat data in some connector topic (stored offset to partition 1 or partition 2).

      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.

            Unassigned Unassigned
            kai.hou kai hou (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: