[
https://issues.apache.org/jira/browse/FLINK-24398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-24398:
-----------------------------------
Labels: pull-request-available stale-minor (was: pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Minor
> Labels: pull-request-available, stale-minor
>
> 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)
