You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Matyas Orhidi (Jira)" <ji...@apache.org> on 2022/03/08 08:35:00 UTC
[jira] [Comment Edited] (FLINK-26521) Reconsider setting generationAwareEventProcessing = true
[ https://issues.apache.org/jira/browse/FLINK-26521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17502800#comment-17502800 ]
Matyas Orhidi edited comment on FLINK-26521 at 3/8/22, 8:34 AM:
----------------------------------------------------------------
We need to think of a clever way to restart the reconcile loop in case of an error, e.g. validation. Annotations provided a way to do this without changing the spec.
was (Author: JIRAUSER282074):
We need to think of a clever way to restart the reconcile loop in case of an error, e.g. validation. Annotations provided a way to to this without changing the spec.
> Reconsider setting generationAwareEventProcessing = true
> --------------------------------------------------------
>
> Key: FLINK-26521
> URL: https://issues.apache.org/jira/browse/FLINK-26521
> Project: Flink
> Issue Type: Sub-task
> Components: Kubernetes Operator
> Reporter: Gyula Fora
> Assignee: Gyula Fora
> Priority: Major
>
> At the moment (if I understand correctly) FlinkDeployment status changes automatically trigger an immediate reconcile step due to havingĀ
> generationAwareEventProcessing = false
> on the FlinkDeploymentController .
> This causes a weird behaviour where reschedule delays and logic around these are not respected properly and many cases.
> This might cause issues as timeout exceptions etc. We should consider whether we need this flag on false.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)