[jira] [Updated] (FLINK-30411) Flink deployment stuck in UPGRADING state when deploy flinkdeployment without resource

[ https://issues.apache.org/jira/browse/FLINK-30411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-30411: --- Fix Version/s: kubernetes-operator-1.4.0 > Flink deployment stuck in UPGRADING state when deploy fli

[jira] [Closed] (FLINK-30411) Flink deployment stuck in UPGRADING state when deploy flinkdeployment without resource

[ https://issues.apache.org/jira/browse/FLINK-30411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora closed FLINK-30411. -- Resolution: Fixed merged to main 4feee47f0175d12ad192fbfc89d483793dcae5b8 > Flink deployment stuck in

[jira] [Updated] (FLINK-30466) Detect ineffective scaling operations

[ https://issues.apache.org/jira/browse/FLINK-30466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-30466: --- Fix Version/s: (was: kubernetes-operator-1.4.0) > Detect ineffective scaling operations > --

[jira] [Closed] (FLINK-30466) Detect ineffective scaling operations

[ https://issues.apache.org/jira/browse/FLINK-30466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora closed FLINK-30466. -- Resolution: Won't Fix I am closing this in order to replace with some more concrete tasks around scal

[jira] [Created] (FLINK-30571) Compute scale parallelism based on observed scalability

Gyula Fora created FLINK-30571: -- Summary: Compute scale parallelism based on observed scalability Key: FLINK-30571 URL: https://issues.apache.org/jira/browse/FLINK-30571 Project: Flink Issue Ty

[jira] [Created] (FLINK-30574) Do not scale further up if last scaling was ineffective

Gyula Fora created FLINK-30574: -- Summary: Do not scale further up if last scaling was ineffective Key: FLINK-30574 URL: https://issues.apache.org/jira/browse/FLINK-30574 Project: Flink Issue Typ

[jira] [Created] (FLINK-30575) Autoscaler doesn't scale down on 0 load

Gyula Fora created FLINK-30575: -- Summary: Autoscaler doesn't scale down on 0 load Key: FLINK-30575 URL: https://issues.apache.org/jira/browse/FLINK-30575 Project: Flink Issue Type: New Feature

[jira] [Closed] (FLINK-29607) Simplify controller flow by introducing FlinkControllerContext

[ https://issues.apache.org/jira/browse/FLINK-29607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora closed FLINK-29607. -- Fix Version/s: kubernetes-operator-1.4.0 Resolution: Fixed merged to main 35604761eac2c75491811

[jira] [Commented] (FLINK-30577) OpenShift FlinkSessionJob artifact write error on non-default namespaces

[ https://issues.apache.org/jira/browse/FLINK-30577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17655131#comment-17655131 ] Gyula Fora commented on FLINK-30577: Or users on open shift could simply configure t

[jira] [Commented] (FLINK-30577) OpenShift FlinkSessionJob artifact write error on non-default namespaces

[ https://issues.apache.org/jira/browse/FLINK-30577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17655285#comment-17655285 ] Gyula Fora commented on FLINK-30577: I just wanted to point out this possiblity as w

[jira] [Created] (FLINK-30593) Determine restart time on the fly for Autoscaler

Gyula Fora created FLINK-30593: -- Summary: Determine restart time on the fly for Autoscaler Key: FLINK-30593 URL: https://issues.apache.org/jira/browse/FLINK-30593 Project: Flink Issue Type: New

[jira] [Updated] (FLINK-30574) Do not scale further up if last scaling was ineffective

[ https://issues.apache.org/jira/browse/FLINK-30574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-30574: --- Component/s: Autoscaler > Do not scale further up if last scaling was ineffective >

[jira] [Updated] (FLINK-30575) Autoscaler doesn't scale down on 0 load

[ https://issues.apache.org/jira/browse/FLINK-30575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-30575: --- Component/s: Autoscaler > Autoscaler doesn't scale down on 0 load >

[jira] [Updated] (FLINK-30571) Compute scale parallelism based on observed scalability

[ https://issues.apache.org/jira/browse/FLINK-30571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-30571: --- Component/s: Autoscaler > Compute scale parallelism based on observed scalability > ---

[jira] [Updated] (FLINK-30594) Update Java version because of JDK bug in the operator

[ https://issues.apache.org/jira/browse/FLINK-30594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-30594: --- Fix Version/s: kubernetes-operator-1.4.0 > Update Java version because of JDK bug in the operator >

[jira] [Updated] (FLINK-30594) Update Java version because of JDK bug in the operator

[ https://issues.apache.org/jira/browse/FLINK-30594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-30594: --- Priority: Critical (was: Blocker) > Update Java version because of JDK bug in the operator > --

[jira] [Commented] (FLINK-30609) Add ephemeral storage to CRD

[ https://issues.apache.org/jira/browse/FLINK-30609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17657075#comment-17657075 ] Gyula Fora commented on FLINK-30609: Are you suggesting simply adding: ``` ephemeral

[jira] [Commented] (FLINK-30609) Add ephemeral storage to CRD

[ https://issues.apache.org/jira/browse/FLINK-30609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17657076#comment-17657076 ] Gyula Fora commented on FLINK-30609: +1 from my part, this indeed seems to be a comm

[jira] [Commented] (FLINK-30638) Operator doesn't forward allowNonRestoredState flag

[ https://issues.apache.org/jira/browse/FLINK-30638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17675593#comment-17675593 ] Gyula Fora commented on FLINK-30638: I think the problem is that last-state mode use

[jira] [Commented] (FLINK-30638) Operator doesn't forward allowNonRestoredState flag

[ https://issues.apache.org/jira/browse/FLINK-30638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17675618#comment-17675618 ] Gyula Fora commented on FLINK-30638: Yes, we set the right configuration but allowNo

[jira] [Commented] (FLINK-30638) Operator doesn't forward allowNonRestoredState flag

[ https://issues.apache.org/jira/browse/FLINK-30638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17675628#comment-17675628 ] Gyula Fora commented on FLINK-30638: Yes, you could do that and that will work. Or y

[jira] [Commented] (FLINK-30518) [flink-operator] Kubernetes HA Service not working with standalone mode

[ https://issues.apache.org/jira/browse/FLINK-30518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17675911#comment-17675911 ] Gyula Fora commented on FLINK-30518: [~usamj] could you please take a look? > [flin

[jira] [Closed] (FLINK-30574) Do not scale further up if last scaling was ineffective

[ https://issues.apache.org/jira/browse/FLINK-30574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora closed FLINK-30574. -- Fix Version/s: kubernetes-operator-1.4.0 Resolution: Fixed merged to main ed6acd453c6e14f7fdb32

[jira] [Created] (FLINK-30652) Use max busytime instead of average to compute true processing rate

Gyula Fora created FLINK-30652: -- Summary: Use max busytime instead of average to compute true processing rate Key: FLINK-30652 URL: https://issues.apache.org/jira/browse/FLINK-30652 Project: Flink

[jira] [Created] (FLINK-30653) Triggere resource Events on autoscaler actions

Gyula Fora created FLINK-30653: -- Summary: Triggere resource Events on autoscaler actions Key: FLINK-30653 URL: https://issues.apache.org/jira/browse/FLINK-30653 Project: Flink Issue Type: New Fe

[jira] [Commented] (FLINK-30213) The edge is wrong when the vertex parallelism is changed

[ https://issues.apache.org/jira/browse/FLINK-30213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17676136#comment-17676136 ] Gyula Fora commented on FLINK-30213: Added a fix for this: fb482fe39844efda33a4c0585

[jira] [Commented] (FLINK-30669) Update recent job status in FlinkDeployment resource object.

[ https://issues.apache.org/jira/browse/FLINK-30669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17676601#comment-17676601 ] Gyula Fora commented on FLINK-30669: The operator doesn't really work for multiple j

[jira] [Created] (FLINK-30680) Consider using the autoscaler to detect slow taskmanagers

Gyula Fora created FLINK-30680: -- Summary: Consider using the autoscaler to detect slow taskmanagers Key: FLINK-30680 URL: https://issues.apache.org/jira/browse/FLINK-30680 Project: Flink Issue T

[jira] [Closed] (FLINK-30652) Use max busytime instead of average to compute true processing rate

[ https://issues.apache.org/jira/browse/FLINK-30652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora closed FLINK-30652. -- Resolution: Fixed merged to main 92034fa912f39f5c8bd57632295c7ca85801f33a > Use max busytime instead

[jira] [Assigned] (FLINK-30609) Add ephemeral storage to CRD

[ https://issues.apache.org/jira/browse/FLINK-30609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora reassigned FLINK-30609: -- Assignee: Zhenqiu Huang (was: Prabcs) > Add ephemeral storage to CRD > -

[jira] [Commented] (FLINK-31798) Add config to enable/disable Kubernetes Events

[ https://issues.apache.org/jira/browse/FLINK-31798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17712260#comment-17712260 ] Gyula Fora commented on FLINK-31798: I don’t really see how events are a performance

[jira] [Commented] (FLINK-31826) Incorrect estimation of the target data rate of a vertex when only a subset of its upstream vertex's output is consumed

[ https://issues.apache.org/jira/browse/FLINK-31826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713178#comment-17713178 ] Gyula Fora commented on FLINK-31826: The same issue can also be easily reproduced wi

[jira] [Commented] (FLINK-31827) Incorrect estimation of the target data rate of a vertex when only a subset of its upstream vertex's output is consumed

[ https://issues.apache.org/jira/browse/FLINK-31827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713181#comment-17713181 ] Gyula Fora commented on FLINK-31827: The same issue can also be easily reproduced wi

[jira] [Commented] (FLINK-31827) Incorrect estimation of the target data rate of a vertex when only a subset of its upstream vertex's output is consumed

[ https://issues.apache.org/jira/browse/FLINK-31827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713197#comment-17713197 ] Gyula Fora commented on FLINK-31827: Exactly, like: target.\{jobvertexId}.numRecord

[jira] [Commented] (FLINK-31769) Add percentiles to aggregated metrics

[ https://issues.apache.org/jira/browse/FLINK-31769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713204#comment-17713204 ] Gyula Fora commented on FLINK-31769: I think this would be a great addition if we ca

[jira] [Assigned] (FLINK-31827) Incorrect estimation of the target data rate of a vertex when only a subset of its upstream vertex's output is consumed

[ https://issues.apache.org/jira/browse/FLINK-31827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora reassigned FLINK-31827: -- Assignee: Gyula Fora > Incorrect estimation of the target data rate of a vertex when only a s

[jira] [Commented] (FLINK-31845) Make KubernetesStepDecorator Pluggable

[ https://issues.apache.org/jira/browse/FLINK-31845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713816#comment-17713816 ] Gyula Fora commented on FLINK-31845: I agree, this is the duplicate of FLINK-28831 a

[jira] [Commented] (FLINK-31794) Ignore unknown CRD fields

[ https://issues.apache.org/jira/browse/FLINK-31794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713907#comment-17713907 ] Gyula Fora commented on FLINK-31794: If we are targeting the cases where the operato

[jira] [Commented] (FLINK-31794) Ignore unknown CRD fields

[ https://issues.apache.org/jira/browse/FLINK-31794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713908#comment-17713908 ] Gyula Fora commented on FLINK-31794: But even then I don't understand how any change

[jira] [Created] (FLINK-31849) Enforce some some simple validation directly through the CRD

Gyula Fora created FLINK-31849: -- Summary: Enforce some some simple validation directly through the CRD Key: FLINK-31849 URL: https://issues.apache.org/jira/browse/FLINK-31849 Project: Flink Iss

[jira] [Created] (FLINK-31852) NumRecordsOut metrics broken

Gyula Fora created FLINK-31852: -- Summary: NumRecordsOut metrics broken Key: FLINK-31852 URL: https://issues.apache.org/jira/browse/FLINK-31852 Project: Flink Issue Type: New Feature Co

[jira] [Updated] (FLINK-31852) NumRecordsOut metrics broken

[ https://issues.apache.org/jira/browse/FLINK-31852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-31852: --- Issue Type: Bug (was: New Feature) > NumRecordsOut metrics broken > >

[jira] [Commented] (FLINK-31852) NumRecordsOut metrics broken

[ https://issues.apache.org/jira/browse/FLINK-31852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17714059#comment-17714059 ] Gyula Fora commented on FLINK-31852: Part of it, but the part related to the chained

[jira] [Commented] (FLINK-31852) NumRecordsOut metrics broken

[ https://issues.apache.org/jira/browse/FLINK-31852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17714060#comment-17714060 ] Gyula Fora commented on FLINK-31852: I will modify the ticket for that   > NumReco

[jira] [Updated] (FLINK-31852) NumRecordsOut metrics broken

[ https://issues.apache.org/jira/browse/FLINK-31852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-31852: --- Description: The numRecordsOut task metrics seem to be incorrect when there are multiple outputs in

[jira] [Updated] (FLINK-31852) NumRecordsOut metrics broken for multiple outout chains

[ https://issues.apache.org/jira/browse/FLINK-31852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-31852: --- Summary: NumRecordsOut metrics broken for multiple outout chains (was: NumRecordsOut metrics broken

[jira] [Commented] (FLINK-31855) Canceling a job through the UI isn't possible in standalone

[ https://issues.apache.org/jira/browse/FLINK-31855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17714118#comment-17714118 ] Gyula Fora commented on FLINK-31855: The cancel button should never exist. > Cancel

[jira] [Commented] (FLINK-31860) FlinkDeployments never finalize when namespace is deleted

[ https://issues.apache.org/jira/browse/FLINK-31860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17714393#comment-17714393 ] Gyula Fora commented on FLINK-31860: Thank you for the detailed analysis , event tri

[jira] [Assigned] (FLINK-31860) FlinkDeployments never finalize when namespace is deleted

[ https://issues.apache.org/jira/browse/FLINK-31860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora reassigned FLINK-31860: -- Assignee: Gyula Fora > FlinkDeployments never finalize when namespace is deleted > --

[jira] [Updated] (FLINK-31860) FlinkDeployments never finalize when namespace is deleted

[ https://issues.apache.org/jira/browse/FLINK-31860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-31860: --- Priority: Blocker (was: Minor) > FlinkDeployments never finalize when namespace is deleted > --

[jira] [Commented] (FLINK-31852) NumRecordsOut metrics broken for multiple outout chains

[ https://issues.apache.org/jira/browse/FLINK-31852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17714517#comment-17714517 ] Gyula Fora commented on FLINK-31852: That is correct [~Weijie Guo] , I will close th

[jira] [Closed] (FLINK-31852) NumRecordsOut metrics broken for multiple outout chains

[ https://issues.apache.org/jira/browse/FLINK-31852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora closed FLINK-31852. -- Resolution: Duplicate Duplicate of https://issues.apache.org/jira/browse/FLINK-18808 > NumRecordsOut

[jira] [Closed] (FLINK-31794) Ignore unknown CRD fields

[ https://issues.apache.org/jira/browse/FLINK-31794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora closed FLINK-31794. -- Fix Version/s: kubernetes-operator-1.5.0 (was: kubernetes-operator-1.4.0)

[jira] [Updated] (FLINK-31845) Make KubernetesStepDecorator Pluggable

[ https://issues.apache.org/jira/browse/FLINK-31845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-31845: --- Issue Type: New Feature (was: Improvement) > Make KubernetesStepDecorator Pluggable > -

[jira] [Updated] (FLINK-31845) Make KubernetesStepDecorator Pluggable

[ https://issues.apache.org/jira/browse/FLINK-31845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-31845: --- Affects Version/s: (was: kubernetes-operator-1.5.0) > Make KubernetesStepDecorator Pluggable > -

[jira] [Created] (FLINK-31869) test_multi_sessionjob.sh gets stuck very frequently

Gyula Fora created FLINK-31869: -- Summary: test_multi_sessionjob.sh gets stuck very frequently Key: FLINK-31869 URL: https://issues.apache.org/jira/browse/FLINK-31869 Project: Flink Issue Type: B

[jira] [Updated] (FLINK-31869) test_multi_sessionjob.sh gets stuck very frequently

[ https://issues.apache.org/jira/browse/FLINK-31869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-31869: --- Description: The test_multi_sessionjob.sh gets stuck almost all the time on recent builds. (was: Th

[jira] [Closed] (FLINK-30609) Add ephemeral storage to CRD

[ https://issues.apache.org/jira/browse/FLINK-30609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora closed FLINK-30609. -- Resolution: Fixed merged to main bad872d04e324fde2b6396e18bae5a37d804f59b > Add ephemeral storage to

[jira] [Assigned] (FLINK-31869) test_multi_sessionjob.sh gets stuck very frequently

[ https://issues.apache.org/jira/browse/FLINK-31869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora reassigned FLINK-31869: -- Assignee: Gyula Fora > test_multi_sessionjob.sh gets stuck very frequently >

[jira] [Closed] (FLINK-31869) test_multi_sessionjob.sh gets stuck very frequently

[ https://issues.apache.org/jira/browse/FLINK-31869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora closed FLINK-31869. -- Fix Version/s: kubernetes-operator-1.5.0 Resolution: Fixed Merged to main 1f54ffa484c359c4b81a4

[jira] [Commented] (FLINK-31827) Incorrect estimation of the target data rate of a vertex when only a subset of its upstream vertex's output is consumed

[ https://issues.apache.org/jira/browse/FLINK-31827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17715078#comment-17715078 ] Gyula Fora commented on FLINK-31827: The first fix on the operator side is merged fo

[jira] [Created] (FLINK-31885) Trigger events on autoscaler errors

Gyula Fora created FLINK-31885: -- Summary: Trigger events on autoscaler errors Key: FLINK-31885 URL: https://issues.apache.org/jira/browse/FLINK-31885 Project: Flink Issue Type: Improvement

[jira] [Created] (FLINK-31886) Upgrade to fabric8 6.5.1 and JOSDK 4.3.0

Gyula Fora created FLINK-31886: -- Summary: Upgrade to fabric8 6.5.1 and JOSDK 4.3.0 Key: FLINK-31886 URL: https://issues.apache.org/jira/browse/FLINK-31886 Project: Flink Issue Type: Improvement

[jira] [Assigned] (FLINK-31886) Upgrade to fabric8 6.5.1 and JOSDK 4.3.0

[ https://issues.apache.org/jira/browse/FLINK-31886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora reassigned FLINK-31886: -- Assignee: Gyula Fora > Upgrade to fabric8 6.5.1 and JOSDK 4.3.0 > ---

[jira] [Assigned] (FLINK-31885) Trigger events on autoscaler errors

[ https://issues.apache.org/jira/browse/FLINK-31885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora reassigned FLINK-31885: -- Assignee: Gyula Fora > Trigger events on autoscaler errors >

[jira] [Updated] (FLINK-31898) Flink k8s autoscaler does not work as expected

[ https://issues.apache.org/jira/browse/FLINK-31898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-31898: --- Component/s: Autoscaler Kubernetes Operator > Flink k8s autoscaler does not work as

[jira] [Commented] (FLINK-31898) Flink k8s autoscaler does not work as expected

[ https://issues.apache.org/jira/browse/FLINK-31898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17715616#comment-17715616 ] Gyula Fora commented on FLINK-31898: cc [~mxm]  > Flink k8s autoscaler does not wor

[jira] [Updated] (FLINK-31898) Flink k8s autoscaler does not work as expected

[ https://issues.apache.org/jira/browse/FLINK-31898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-31898: --- Issue Type: Bug (was: Improvement) > Flink k8s autoscaler does not work as expected > -

[jira] [Updated] (FLINK-31898) Flink k8s autoscaler does not work as expected

[ https://issues.apache.org/jira/browse/FLINK-31898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-31898: --- Affects Version/s: kubernetes-operator-1.4.0 > Flink k8s autoscaler does not work as expected >

[jira] [Updated] (FLINK-31924) [Flink operator] Flink Autoscale - Limit the max number of scale ups

[ https://issues.apache.org/jira/browse/FLINK-31924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-31924: --- Component/s: Autoscaler Kubernetes Operator > [Flink operator] Flink Autoscale - Li

[jira] [Updated] (FLINK-31924) [Flink operator] Flink Autoscale - Limit the max number of scale ups

[ https://issues.apache.org/jira/browse/FLINK-31924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-31924: --- Issue Type: Bug (was: Improvement) > [Flink operator] Flink Autoscale - Limit the max number of sca

[jira] [Commented] (FLINK-31924) [Flink operator] Flink Autoscale - Limit the max number of scale ups

[ https://issues.apache.org/jira/browse/FLINK-31924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17715777#comment-17715777 ] Gyula Fora commented on FLINK-31924: cc [~mxm]  > [Flink operator] Flink Autoscale

[jira] [Commented] (FLINK-31924) [Flink operator] Flink Autoscale - Limit the max number of scale ups

[ https://issues.apache.org/jira/browse/FLINK-31924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17715779#comment-17715779 ] Gyula Fora commented on FLINK-31924: [~sriramgr] can you please try the autoscaler f

[jira] [Commented] (FLINK-31898) Flink k8s autoscaler does not work as expected

[ https://issues.apache.org/jira/browse/FLINK-31898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17716096#comment-17716096 ] Gyula Fora commented on FLINK-31898: I am a bit confused here by all the graphs :) B

[jira] [Closed] (FLINK-31924) [Flink operator] Flink Autoscale - Limit the max number of scale ups

[ https://issues.apache.org/jira/browse/FLINK-31924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora closed FLINK-31924. -- Resolution: Not A Bug Based on offline discussion the problem seems to be related to the job itself n

[jira] [Commented] (FLINK-31936) Support setting scale up max factor

[ https://issues.apache.org/jira/browse/FLINK-31936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17716271#comment-17716271 ] Gyula Fora commented on FLINK-31936: Thanks [~Zhanghao Chen] , I assign this to you

[jira] [Assigned] (FLINK-31936) Support setting scale up max factor

[ https://issues.apache.org/jira/browse/FLINK-31936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora reassigned FLINK-31936: -- Assignee: Zhanghao Chen > Support setting scale up max factor > -

[jira] [Commented] (FLINK-31898) Flink k8s autoscaler does not work as expected

[ https://issues.apache.org/jira/browse/FLINK-31898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17716551#comment-17716551 ] Gyula Fora commented on FLINK-31898: Thats good to hear [~lufovic77] I will close th

[jira] [Closed] (FLINK-31898) Flink k8s autoscaler does not work as expected

[ https://issues.apache.org/jira/browse/FLINK-31898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora closed FLINK-31898. -- Resolution: Not A Problem > Flink k8s autoscaler does not work as expected > -

[jira] [Commented] (FLINK-31860) FlinkDeployments never finalize when namespace is deleted

[ https://issues.apache.org/jira/browse/FLINK-31860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17716805#comment-17716805 ] Gyula Fora commented on FLINK-31860: [~isugimpy] , the PR is ready, please help revi

[jira] [Commented] (FLINK-31860) FlinkDeployments never finalize when namespace is deleted

[ https://issues.apache.org/jira/browse/FLINK-31860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17717055#comment-17717055 ] Gyula Fora commented on FLINK-31860: I have to put this work on hold for now because

[jira] [Assigned] (FLINK-31947) Enable stdout redirect in flink-console.sh

[ https://issues.apache.org/jira/browse/FLINK-31947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora reassigned FLINK-31947: -- Assignee: Zhenqiu Huang > Enable stdout redirect in flink-console.sh > --

[jira] [Commented] (FLINK-30773) Add API for rescaling of jobs based on per-vertex parallelism overrides

[ https://issues.apache.org/jira/browse/FLINK-30773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17717458#comment-17717458 ] Gyula Fora commented on FLINK-30773: I think the features outlined in this ticket ar

[jira] [Closed] (FLINK-31885) Trigger events on autoscaler errors

[ https://issues.apache.org/jira/browse/FLINK-31885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora closed FLINK-31885. -- Resolution: Fixed merged to main 41f753fec40121274c8d0b27f327ffbd52500cf7 > Trigger events on autosca

[jira] [Commented] (FLINK-31964) Improve the document of Autoscaler as 1.17.0 is released

[ https://issues.apache.org/jira/browse/FLINK-31964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17717635#comment-17717635 ] Gyula Fora commented on FLINK-31964: In addition we should also improve the docs for

[jira] [Closed] (FLINK-31845) Make KubernetesStepDecorator Pluggable

[ https://issues.apache.org/jira/browse/FLINK-31845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora closed FLINK-31845. -- Resolution: Duplicate [~darenwkt] can you please help review on the original ticket https://issues.ap

[jira] [Commented] (FLINK-28831) [3] Support pluginable decorators mechanism

[ https://issues.apache.org/jira/browse/FLINK-28831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17718189#comment-17718189 ] Gyula Fora commented on FLINK-28831: [~bzhaoop] are you still working on this or can

[jira] [Updated] (FLINK-31963) java.lang.ArrayIndexOutOfBoundsException when scaling down

[ https://issues.apache.org/jira/browse/FLINK-31963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-31963: --- Summary: java.lang.ArrayIndexOutOfBoundsException when scaling down (was: java.lang.ArrayIndexOutOf

[jira] [Updated] (FLINK-31963) java.lang.ArrayIndexOutOfBoundsException when scaling down with unaligned checkpoints

[ https://issues.apache.org/jira/browse/FLINK-31963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-31963: --- Summary: java.lang.ArrayIndexOutOfBoundsException when scaling down with unaligned checkpoints (was

[jira] [Commented] (FLINK-31976) Once marked as an inefficient scale-up, further scaling may not happen forever

[ https://issues.apache.org/jira/browse/FLINK-31976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17718192#comment-17718192 ] Gyula Fora commented on FLINK-31976: We have some logic in the `addToScalingHistory`

[jira] [Commented] (FLINK-31977) If scaling.effectiveness.detection.enabled is false, the call to the detectIneffectiveScaleUp() function is unnecessary

[ https://issues.apache.org/jira/browse/FLINK-31977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17718194#comment-17718194 ] Gyula Fora commented on FLINK-31977: The logic here is that we trigger an Event even

[jira] [Commented] (FLINK-31966) Flink Kubernetes operator lacks TLS support

[ https://issues.apache.org/jira/browse/FLINK-31966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17718195#comment-17718195 ] Gyula Fora commented on FLINK-31966: Thank you [~adrianalexvasiliu] . We have not he

[jira] [Commented] (FLINK-31941) Not backwards compatible naming for some kubernetes resources

[ https://issues.apache.org/jira/browse/FLINK-31941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17718196#comment-17718196 ] Gyula Fora commented on FLINK-31941: Flink itself doesn't come with standalone deplo

[jira] [Updated] (FLINK-31941) Not backwards compatible naming for some kubernetes resources

[ https://issues.apache.org/jira/browse/FLINK-31941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-31941: --- Issue Type: Improvement (was: Bug) > Not backwards compatible naming for some kubernetes resources

[jira] [Commented] (FLINK-31976) Once marked as an inefficient scale-up, further scaling may not happen forever

[ https://issues.apache.org/jira/browse/FLINK-31976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17718221#comment-17718221 ] Gyula Fora commented on FLINK-31976: We have to distinguish 2 things here.  1. Scal

[jira] [Commented] (FLINK-31976) Once marked as an inefficient scale-up, further scaling may not happen forever

[ https://issues.apache.org/jira/browse/FLINK-31976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17718275#comment-17718275 ] Gyula Fora commented on FLINK-31976: Just because the source true processing rate do

[jira] [Commented] (FLINK-31976) Once marked as an inefficient scale-up, further scaling may not happen forever

[ https://issues.apache.org/jira/browse/FLINK-31976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17718319#comment-17718319 ] Gyula Fora commented on FLINK-31976: Based on the metrics:   - NumRecords in didn't

[jira] [Commented] (FLINK-31982) Build image from source Dockerfile error in main

[ https://issues.apache.org/jira/browse/FLINK-31982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17718790#comment-17718790 ] Gyula Fora commented on FLINK-31982: Strange error, haven’t seen this before. We did

[jira] [Updated] (FLINK-31795) Add Config to enable/disable savepoint cleanup

[ https://issues.apache.org/jira/browse/FLINK-31795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-31795: --- Fix Version/s: kubernetes-operator-1.5.0 (was: kubernetes-operator-1.4.0) > A

[jira] [Closed] (FLINK-31795) Add Config to enable/disable savepoint cleanup

[ https://issues.apache.org/jira/browse/FLINK-31795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora closed FLINK-31795. -- Resolution: Fixed merged to main 6df91ae17873c274b2b993ab7bef30f1297e5c3e > Add Config to enable/disa

<    9   10   11   12   13   14   15   16   17   18   >