Slow catch-up when many archivelogs need to be consumed

When many archivelog files need to catch up. If a database log switch occurs, the connector will restart the logminer session and reload the log files even if many archivelogs are not consumed. This happens frequently during the catch-up process, and it takes a lot of time to load the logfile, which affects the catch-up efficiency.

My connector starts with about 100+(About 1.5T) archivelogs to catch up, . The database log switch triggers the restart of logminer and addlogFile, which consumes a lot of time each time. I can't catch up with the latest database log.

I recommend not needing to load onlinelog and check database Log Switch before processing all archivelogs that need to catch up