[ https://issues.apache.org/jira/browse/FLINK-24398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-24398: ----------------------------------- Labels: auto-deprioritized-minor pull-request-available (was: pull-request-available stale-minor) Priority: Not a Priority (was: Minor) This issue was labeled "stale-minor" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Minor, please raise the priority and ask a committer to assign you the issue or revive the public discussion. > KafkaSourceFetcherManager should re-use an existing SplitFetcher to commit > offset if possible > --------------------------------------------------------------------------------------------- > > Key: FLINK-24398 > URL: https://issues.apache.org/jira/browse/FLINK-24398 > Project: Flink > Issue Type: Improvement > Reporter: Dong Lin > Priority: Not a Priority > Labels: auto-deprioritized-minor, pull-request-available > > Currently KafkaSourceFetcherManager::commitOffset() will create a new > SplitFetcher if the fetchers.get(0) == null. As a result, if the first > fetcher has already been closed and removed, N fetchers will be created for N > commitOffset() invocations. > A more efficient approach is to re-use an existing fetcher to commit the > offset if there is any running fetchers in this KafkaSourceFetcherManager. -- This message was sent by Atlassian Jira (v8.20.1#820001)