xyw0537 commented on PR #2220: URL: https://github.com/apache/flink-cdc/pull/2220#issuecomment-2989397442
@wallkop @PatrickRen I believe the fix logic for the gtid.new.channel.position=EARLIEST configuration should equally apply to LATEST. Let’s examine this example. 1.Obtain the available GTIDs, i.e., show master status. ``` 106a4bb6-ec0d-11ec-a2d4-00163e279211:1-204479617, 7aec1281-719c-11eb-afcf-00163e06a35c:1-147359662 ``` 2.Obtain the checkpoint GTIDs. ``` 106a4bb6-ec0d-11ec-a2d4-00163e279211:203495054-204182173 ``` 3.Obtain the purged GTIDs, i.e., @@global.gtid_purged. ``` 106a4bb6-ec0d-11ec-a2d4-00163e279211:1-203495053, 7aec1281-719c-11eb-afcf-00163e06a35c:1-147359662 ``` When gtid.new.channel.position=**EARLIEST**, mergedGtidSet whould be ``` 106a4bb6-ec0d-11ec-a2d4-00163e279211:1-204182173 7aec1281-719c-11eb-afcf-00163e06a35c:1-147359662 ``` When gtid.new.channel.position=**LATEST**, mergedGtidSet whould be ``` 106a4bb6-ec0d-11ec-a2d4-00163e279211:203495054-204182173 ``` The gtid.new.channel.position configuration should only affect new channels. In the example above, only 7aec1281-719c-11eb-afcf-00163e06a35c is the new channel. Therefore, the results for UUID 106a4bb6-ec0d-11ec-a2d4-00163e279211 should remain unchanged. I believe when LATEST is configured, the mergedGtidSet should be ``` 106a4bb6-ec0d-11ec-a2d4-00163e279211:1-204182173 ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
