[
https://issues.apache.org/jira/browse/FLINK-22108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-22108:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major 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.
> Ephemeral socket address was checkpointed to state and restored back in
> CollectSinkOperatorCoordinator
> ------------------------------------------------------------------------------------------------------
>
> Key: FLINK-22108
> URL: https://issues.apache.org/jira/browse/FLINK-22108
> Project: Flink
> Issue Type: Bug
> Components: API / DataStream
> Affects Versions: 1.13.0
> Reporter: Kezhu Wang
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> {{CollectSinkOperatorCoordinator}} checkpointed its {{address}} field to
> state and restored back. That field is listener address of
> {{CollectSinkFunction}}. After {{resetToCheckpoint}} (eg. global failover}},
> {{address}} is meaningless. If client request comes before
> {{CollectSinkAddressEvent}}, it will use that meaningless address for
> connection. In best situation, error happens, and nothing hurts. In bad
> situation, no one knows where the restored address points to now.
> cc [~TsReaper] [~ykt836]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
