[
https://issues.apache.org/jira/browse/FLINK-21667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17324103#comment-17324103
]
Flink Jira Bot commented on FLINK-21667:
----------------------------------------
This issue is assigned but has not received an update in 7 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> Standby RM might remove resources from Kubernetes
> -------------------------------------------------
>
> Key: FLINK-21667
> URL: https://issues.apache.org/jira/browse/FLINK-21667
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Kubernetes, Runtime / Coordination
> Affects Versions: 1.12.2
> Reporter: Xintong Song
> Assignee: Xintong Song
> Priority: Major
> Labels: pull-request-available, stale-assigned
> Fix For: 1.14.0
>
>
> Currently, on initialization {{KubernetesResourceManagerDriver}} starts a
> watch for receiving pod events. It could happen that it starts to receive
> events before obtaining leadership. Consequently, a standby RM may remove
> terminated pods from Kubernetes during handling the events.
> This is not very damaging atm, since the removed pods are already terminated
> anyway. However, it would still be good for a standby RM to strictly
> following the contract and make no modifications before obtaining leadership.
> We might consider to postpone starting of the watch to when the leadership is
> granted.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
