[
https://issues.apache.org/jira/browse/FLINK-21921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-21921:
-----------------------------------
Labels: stale-major (was: )
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
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Unreasonable ADDED event ignoring in callback handler in
> KubernetesLeaderRetrievalDriver
> ----------------------------------------------------------------------------------------
>
> Key: FLINK-21921
> URL: https://issues.apache.org/jira/browse/FLINK-21921
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Kubernetes
> Reporter: Yi Tang
> Priority: Major
> Labels: stale-major
>
> The comment is not exactly accurate in case of JM restarting or ConfigMap
> watching restarting(KubernetesTooOldResourceVersionException)
> {code:java}
> private class ConfigMapCallbackHandlerImpl
> implements
> FlinkKubeClient.WatchCallbackHandler<KubernetesConfigMap> {
> @Override
> public void onAdded(List<KubernetesConfigMap> configMaps) {
> // The ConfigMap is created by KubernetesLeaderElectionDriver
> with empty data. We do not
> // process this
> // useless event.
> }
> {code}
> Maybe we should handle it like onModified.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
