[jira] [Closed] (FLINK-34574) Add CPU and memory size autoscaler quota

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

[jira] [Created] (FLINK-35157) Sources with watermark alignment get stuck once some subtasks finish

Gyula Fora created FLINK-35157: -- Summary: Sources with watermark alignment get stuck once some subtasks finish Key: FLINK-35157 URL: https://issues.apache.org/jira/browse/FLINK-35157 Project: Flink

[jira] [Closed] (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 closed FLINK-31860. -- Fix Version/s: kubernetes-operator-1.9.0 Assignee: Zhou JIANG (was: Jayme Howard)

[jira] [Created] (FLINK-35126) Improve checkpoint progress health check config and enable by default

Gyula Fora created FLINK-35126: -- Summary: Improve checkpoint progress health check config and enable by default Key: FLINK-35126 URL: https://issues.apache.org/jira/browse/FLINK-35126 Project: Flink

[jira] [Commented] (FLINK-35123) Flink Kubernetes Operator should not do deleteHAData

[ https://issues.apache.org/jira/browse/FLINK-35123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837610#comment-17837610 ] Gyula Fora commented on FLINK-35123: I agree that if the rest api is accessible we could call

[jira] [Closed] (FLINK-35108) Deployment recovery is triggered on terminal jobs after jm shutdown ttl

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

[jira] [Created] (FLINK-35108) Deployment recovery is triggered on terminal jobs after jm shutdown ttl

Gyula Fora created FLINK-35108: -- Summary: Deployment recovery is triggered on terminal jobs after jm shutdown ttl Key: FLINK-35108 URL: https://issues.apache.org/jira/browse/FLINK-35108 Project: Flink

[jira] [Comment Edited] (FLINK-34704) Process checkpoint barrier in AsyncWaitOperator when the element queue is full

[ https://issues.apache.org/jira/browse/FLINK-34704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836106#comment-17836106 ] Gyula Fora edited comment on FLINK-34704 at 4/11/24 10:41 AM: -- I agree with

[jira] [Commented] (FLINK-34704) Process checkpoint barrier in AsyncWaitOperator when the element queue is full

[ https://issues.apache.org/jira/browse/FLINK-34704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836107#comment-17836107 ] Gyula Fora commented on FLINK-34704: So restricting the optimisation to the head of the operator

[jira] [Commented] (FLINK-34704) Process checkpoint barrier in AsyncWaitOperator when the element queue is full

[ https://issues.apache.org/jira/browse/FLINK-34704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836106#comment-17836106 ] Gyula Fora commented on FLINK-34704: I agree with [~pnowojski] here, the currently blocked element

[jira] [Updated] (FLINK-34947) Reduce JM scale down timeout

[ https://issues.apache.org/jira/browse/FLINK-34947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-34947: --- Description: We introduced a logic to scale down the JobManager before the task managers are

[jira] [Updated] (FLINK-34947) Reduce JM scale down timeout

[ https://issues.apache.org/jira/browse/FLINK-34947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-34947: --- Description: We introduced a logic to scale down the JobManager before the task managers are

[jira] [Updated] (FLINK-34947) Reduce JM scale down timeout

[ https://issues.apache.org/jira/browse/FLINK-34947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-34947: --- Summary: Reduce JM scale down timeout (was: Do not scale down JM in Orphan deletion propagation

[jira] [Created] (FLINK-34947) Do not scale down JM in Orphan deletion propagation and reduce timeout

Gyula Fora created FLINK-34947: -- Summary: Do not scale down JM in Orphan deletion propagation and reduce timeout Key: FLINK-34947 URL: https://issues.apache.org/jira/browse/FLINK-34947 Project: Flink

[jira] [Commented] (FLINK-32529) Optional startup probe for JM deployment

[ https://issues.apache.org/jira/browse/FLINK-32529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830805#comment-17830805 ] Gyula Fora commented on FLINK-32529: [~tbnguyen1407] please open a separate Jira ticket for this. If

[jira] [Commented] (FLINK-34927) Translate flink-kubernetes-operator documentation

[ https://issues.apache.org/jira/browse/FLINK-34927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830364#comment-17830364 ] Gyula Fora commented on FLINK-34927: I think this would be great, I won't be able to review the

[jira] [Commented] (FLINK-34907) jobRunningTs should be the timestamp that all tasks are running

[ https://issues.apache.org/jira/browse/FLINK-34907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17829467#comment-17829467 ] Gyula Fora commented on FLINK-34907: similar to the other Jirayou opened this only seems to affect

[jira] [Closed] (FLINK-34228) Add long UTF serializer/deserializer

[ https://issues.apache.org/jira/browse/FLINK-34228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora closed FLINK-34228. -- Fix Version/s: 1.20.0 Resolution: Fixed merged to master

[jira] [Commented] (FLINK-34728) operator does not need to upload and download the jar when deploying session job

[ https://issues.apache.org/jira/browse/FLINK-34728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17828222#comment-17828222 ] Gyula Fora commented on FLINK-34728: That makes sense, however this is more a ticket for Flink core

[jira] [Commented] (FLINK-34726) Flink Kubernetes Operator has some room for optimizing performance.

[ https://issues.apache.org/jira/browse/FLINK-34726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17828210#comment-17828210 ] Gyula Fora commented on FLINK-34726: Thanks for the detailed analysis [~Fei Feng] . You are

[jira] [Commented] (FLINK-34655) Autoscaler doesn't work for flink 1.15

[ https://issues.apache.org/jira/browse/FLINK-34655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17826054#comment-17826054 ] Gyula Fora commented on FLINK-34655: [~mxm] I would be hesitant to try to backport these changes to

[jira] [Comment Edited] (FLINK-34655) Autoscaler doesn't work for flink 1.15

[ https://issues.apache.org/jira/browse/FLINK-34655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17825657#comment-17825657 ] Gyula Fora edited comment on FLINK-34655 at 3/12/24 12:12 PM: -- Also this

[jira] [Commented] (FLINK-34655) Autoscaler doesn't work for flink 1.15

[ https://issues.apache.org/jira/browse/FLINK-34655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17825657#comment-17825657 ] Gyula Fora commented on FLINK-34655: Also this issue is fixed in the Kubernetes-operator package

[jira] [Updated] (FLINK-34655) Autoscaler doesn't work for flink 1.15

[ https://issues.apache.org/jira/browse/FLINK-34655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-34655: --- Priority: Major (was: Blocker) > Autoscaler doesn't work for flink 1.15 >

[jira] [Commented] (FLINK-34655) Autoscaler doesn't work for flink 1.15

[ https://issues.apache.org/jira/browse/FLINK-34655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17825656#comment-17825656 ] Gyula Fora commented on FLINK-34655: But the vertex parallelism overrides feature was introduced in

[jira] [Commented] (FLINK-34655) Autoscaler doesn't work for flink 1.15

[ https://issues.apache.org/jira/browse/FLINK-34655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17825655#comment-17825655 ] Gyula Fora commented on FLINK-34655: The bigger issue is that aggregated busy time metrics are not

[jira] [Closed] (FLINK-34524) Scale down JobManager deployment to 0 before deletion

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

[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=17825414#comment-17825414 ] Gyula Fora commented on FLINK-31860: I don’t really know how that would be possible but I welcome

[jira] [Commented] (FLINK-34563) Autoscaling decision improvement

[ https://issues.apache.org/jira/browse/FLINK-34563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17825380#comment-17825380 ] Gyula Fora commented on FLINK-34563: Copying over my comment from GitHub for completeness: I have

[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=17825379#comment-17825379 ] Gyula Fora commented on FLINK-31860: I am not aware of any solution from the kubernetes / josdk side

[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: Major (was: Blocker) > FlinkDeployments never finalize when namespace is deleted >

[jira] [Closed] (FLINK-34566) Flink Kubernetes Operator reconciliation parallelism setting not work

[ https://issues.apache.org/jira/browse/FLINK-34566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora closed FLINK-34566. -- Resolution: Fixed merged to main 726e484c6a9b4121563829bc094b3eebeb8ddcf3 > Flink Kubernetes

[jira] [Updated] (FLINK-34566) Flink Kubernetes Operator reconciliation parallelism setting not work

[ https://issues.apache.org/jira/browse/FLINK-34566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-34566: --- Fix Version/s: kubernetes-operator-1.8.0 > Flink Kubernetes Operator reconciliation parallelism

[jira] [Closed] (FLINK-34580) Job run via REST erases "pipeline.classpaths" config

[ https://issues.apache.org/jira/browse/FLINK-34580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora closed FLINK-34580. -- Resolution: Fixed merged to main d0ce5349fdf1a611518eba20a169c475ee0b46c5 > Job run via REST erases

[jira] [Assigned] (FLINK-34580) Job run via REST erases "pipeline.classpaths" config

[ https://issues.apache.org/jira/browse/FLINK-34580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora reassigned FLINK-34580: -- Assignee: Ferenc Csaky > Job run via REST erases "pipeline.classpaths" config >

[jira] [Created] (FLINK-34619) Do not wait for scaling completion in UPGRADE state with in-place scaling

Gyula Fora created FLINK-34619: -- Summary: Do not wait for scaling completion in UPGRADE state with in-place scaling Key: FLINK-34619 URL: https://issues.apache.org/jira/browse/FLINK-34619 Project: Flink

[jira] [Commented] (FLINK-34576) Flink deployment keep staying at RECONCILING/STABLE status

[ https://issues.apache.org/jira/browse/FLINK-34576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17824297#comment-17824297 ] Gyula Fora commented on FLINK-34576: Ah I see, I thought the issue you linked was a fix for this

[jira] [Commented] (FLINK-34588) FineGrainedSlotManager checks whether resources need to reconcile but doesn't act on the result

[ https://issues.apache.org/jira/browse/FLINK-34588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17824082#comment-17824082 ] Gyula Fora commented on FLINK-34588: The links in the description don't seem to work :/  >

[jira] [Commented] (FLINK-34576) Flink deployment keep staying at RECONCILING/STABLE status

[ https://issues.apache.org/jira/browse/FLINK-34576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17824041#comment-17824041 ] Gyula Fora commented on FLINK-34576: I am happy to review your PR if you try to bump the version >

[jira] [Commented] (FLINK-34576) Flink deployment keep staying at RECONCILING/STABLE status

[ https://issues.apache.org/jira/browse/FLINK-34576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17824039#comment-17824039 ] Gyula Fora commented on FLINK-34576: I think what you found could definitely explain the problem, so

[jira] [Commented] (FLINK-34576) Flink deployment keep staying at RECONCILING/STABLE status

[ https://issues.apache.org/jira/browse/FLINK-34576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17824038#comment-17824038 ] Gyula Fora commented on FLINK-34576: Not sure how to repro this in a test easily, you could try

[jira] [Commented] (FLINK-34566) Flink Kubernetes Operator reconciliation parallelism setting not work

[ https://issues.apache.org/jira/browse/FLINK-34566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823682#comment-17823682 ] Gyula Fora commented on FLINK-34566: [~Fei Feng] here is the JOSDK side fix, can you please help

[jira] [Comment Edited] (FLINK-34576) Flink deployment keep staying at RECONCILING/STABLE status

[ https://issues.apache.org/jira/browse/FLINK-34576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823613#comment-17823613 ] Gyula Fora edited comment on FLINK-34576 at 3/5/24 1:19 PM: I am a bit busy

[jira] [Commented] (FLINK-34576) Flink deployment keep staying at RECONCILING/STABLE status

[ https://issues.apache.org/jira/browse/FLINK-34576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823613#comment-17823613 ] Gyula Fora commented on FLINK-34576: I am a bit busy at the moment so it will take some time until I

[jira] [Updated] (FLINK-34576) Flink deployment keep staying at RECONCILING/STABLE status

[ https://issues.apache.org/jira/browse/FLINK-34576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-34576: --- Description: The HA mode of flink-kubernetes-operator is being used. When one of the pods of

[jira] [Assigned] (FLINK-34566) Flink Kubernetes Operator reconciliation parallelism setting not work

[ https://issues.apache.org/jira/browse/FLINK-34566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora reassigned FLINK-34566: -- Assignee: Fei Feng > Flink Kubernetes Operator reconciliation parallelism setting not work >

[jira] [Commented] (FLINK-34566) Flink Kubernetes Operator reconciliation parallelism setting not work

[ https://issues.apache.org/jira/browse/FLINK-34566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823457#comment-17823457 ] Gyula Fora commented on FLINK-34566: Thanks [~Fei Feng] ! > Flink Kubernetes Operator

[jira] [Comment Edited] (FLINK-34566) Flink Kubernetes Operator reconciliation parallelism setting not work

[ https://issues.apache.org/jira/browse/FLINK-34566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823433#comment-17823433 ] Gyula Fora edited comment on FLINK-34566 at 3/5/24 6:02 AM: Thanks for the

[jira] [Commented] (FLINK-34566) Flink Kubernetes Operator reconciliation parallelism setting not work

[ https://issues.apache.org/jira/browse/FLINK-34566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823433#comment-17823433 ] Gyula Fora commented on FLINK-34566: Thanks for the detailed explanation, I missed this part. Sounds

[jira] [Closed] (FLINK-34566) Flink Kubernetes Operator reconciliation parallelism setting not work

[ https://issues.apache.org/jira/browse/FLINK-34566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora closed FLINK-34566. -- Resolution: Not A Problem I am closing this ticket for now, if you feel that this resolution is

[jira] [Commented] (FLINK-33992) Add option to fetch the jar from private repository in FlinkSessionJob

[ https://issues.apache.org/jira/browse/FLINK-33992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823169#comment-17823169 ] Gyula Fora commented on FLINK-33992: It would be great if Flink itself would have a way of

[jira] [Commented] (FLINK-33992) Add option to fetch the jar from private repository in FlinkSessionJob

[ https://issues.apache.org/jira/browse/FLINK-33992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823168#comment-17823168 ] Gyula Fora commented on FLINK-33992: For session job submissions the jar generally has to be

[jira] [Commented] (FLINK-34566) Flink Kubernetes Operator reconciliation parallelism setting not work

[ https://issues.apache.org/jira/browse/FLINK-34566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823165#comment-17823165 ] Gyula Fora commented on FLINK-34566: {noformat} A ThreadPoolExecutor will automatically adjust the

[jira] [Commented] (FLINK-34566) Flink Kubernetes Operator reconciliation parallelism setting not work

[ https://issues.apache.org/jira/browse/FLINK-34566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823166#comment-17823166 ] Gyula Fora commented on FLINK-34566: >From the java docs: "A ThreadPoolExecutor will automatically

[jira] (FLINK-34566) Flink Kubernetes Operator reconciliation parallelism setting not work

[ https://issues.apache.org/jira/browse/FLINK-34566 ] Gyula Fora deleted comment on FLINK-34566: was (Author: gyfora): {noformat} A ThreadPoolExecutor will automatically adjust the pool size (see getPoolSize) according to the bounds set by

[jira] [Commented] (FLINK-34566) Flink Kubernetes Operator reconciliation parallelism setting not work

[ https://issues.apache.org/jira/browse/FLINK-34566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823164#comment-17823164 ] Gyula Fora commented on FLINK-34566: Even if the core pool size is 10, the maxpoolsize defines how

[jira] [Commented] (FLINK-34566) Flink Kubernetes Operator reconciliation parallelism setting not work

[ https://issues.apache.org/jira/browse/FLINK-34566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823163#comment-17823163 ] Gyula Fora commented on FLINK-34566: Looking at this in detail I think it should work as expected.

[jira] [Commented] (FLINK-34566) Flink Kubernetes Operator reconciliation parallelism setting not work

[ https://issues.apache.org/jira/browse/FLINK-34566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823049#comment-17823049 ] Gyula Fora commented on FLINK-34566: You are saying that this is a bug in the JOSDK ? 

[jira] [Closed] (FLINK-34561) Downgrading flink-kubernetes-operator causes failure

[ https://issues.apache.org/jira/browse/FLINK-34561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora closed FLINK-34561. -- Resolution: Not A Problem This works as expected. CRD and the operator is backward compatible, not

[jira] [Commented] (FLINK-34524) Scale down JobManager deployment to 0 before deletion

[ https://issues.apache.org/jira/browse/FLINK-34524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820991#comment-17820991 ] Gyula Fora commented on FLINK-34524: cc [~mateczagany]  > Scale down JobManager deployment to 0

[jira] [Created] (FLINK-34524) Scale down JobManager deployment to 0 before deletion

Gyula Fora created FLINK-34524: -- Summary: Scale down JobManager deployment to 0 before deletion Key: FLINK-34524 URL: https://issues.apache.org/jira/browse/FLINK-34524 Project: Flink Issue

[jira] [Commented] (FLINK-34451) [Kubernetes Operator] Job with restarting TaskManagers uses wrong/misleading fallback approach

[ https://issues.apache.org/jira/browse/FLINK-34451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820657#comment-17820657 ] Gyula Fora commented on FLINK-34451: I opened a new ticket to track this issue explicitly for the

[jira] [Commented] (FLINK-34518) Adaptive Scheduler restores from empty state if JM fails during restarting state

[ https://issues.apache.org/jira/browse/FLINK-34518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820656#comment-17820656 ] Gyula Fora commented on FLINK-34518: cc [~mapohl] [~chesnay]  > Adaptive Scheduler restores from

[jira] [Created] (FLINK-34518) Adaptive Scheduler restores from empty state if JM fails during restarting state

Gyula Fora created FLINK-34518: -- Summary: Adaptive Scheduler restores from empty state if JM fails during restarting state Key: FLINK-34518 URL: https://issues.apache.org/jira/browse/FLINK-34518

[jira] [Commented] (FLINK-34451) [Kubernetes Operator] Job with restarting TaskManagers uses wrong/misleading fallback approach

[ https://issues.apache.org/jira/browse/FLINK-34451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820622#comment-17820622 ] Gyula Fora commented on FLINK-34451: It looks like there is a race condition between handling the

[jira] [Commented] (FLINK-34451) [Kubernetes Operator] Job with restarting TaskManagers uses wrong/misleading fallback approach

[ https://issues.apache.org/jira/browse/FLINK-34451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820604#comment-17820604 ] Gyula Fora commented on FLINK-34451: I took a closer look at this and it also happens with the

[jira] [Commented] (FLINK-34451) [Kubernetes Operator] Job with restarting TaskManagers uses wrong/misleading fallback approach

[ https://issues.apache.org/jira/browse/FLINK-34451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820276#comment-17820276 ] Gyula Fora commented on FLINK-34451: I will definitely try this on Monday , I was just curious if

[jira] [Commented] (FLINK-34451) [Kubernetes Operator] Job with restarting TaskManagers uses wrong/misleading fallback approach

[ https://issues.apache.org/jira/browse/FLINK-34451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820272#comment-17820272 ] Gyula Fora commented on FLINK-34451: To me the logs are not very surprising. The way it is currently

[jira] [Commented] (FLINK-34451) [Kubernetes Operator] Job with restarting TaskManagers uses wrong/misleading fallback approach

[ https://issues.apache.org/jira/browse/FLINK-34451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820209#comment-17820209 ] Gyula Fora commented on FLINK-34451: That's a good catch, if this is a bug related to adaptive

[jira] [Commented] (FLINK-29696) [Doc] Operator helm install command points to wrong repo

[ https://issues.apache.org/jira/browse/FLINK-29696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17819941#comment-17819941 ] Gyula Fora commented on FLINK-29696: [~domenicbove] feel free to open a doc improvement PR if you

[jira] [Commented] (FLINK-34451) [Kubernetes Operator] Job with restarting TaskManagers uses wrong/misleading fallback approach

[ https://issues.apache.org/jira/browse/FLINK-34451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17819826#comment-17819826 ] Gyula Fora commented on FLINK-34451: Also one thing that occurred to me is that the issue could be

[jira] [Commented] (FLINK-34451) [Kubernetes Operator] Job with restarting TaskManagers uses wrong/misleading fallback approach

[ https://issues.apache.org/jira/browse/FLINK-34451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17819810#comment-17819810 ] Gyula Fora commented on FLINK-34451: I tried killing TMs and immediately bumping the restartNonce at

[jira] [Commented] (FLINK-34451) [Kubernetes Operator] Job with restarting TaskManagers uses wrong/misleading fallback approach

[ https://issues.apache.org/jira/browse/FLINK-34451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17819807#comment-17819807 ] Gyula Fora commented on FLINK-34451: Hm, so this really seems to be somehow adaptive scheduler

[jira] [Comment Edited] (FLINK-34451) [Kubernetes Operator] Job with restarting TaskManagers uses wrong/misleading fallback approach

[ https://issues.apache.org/jira/browse/FLINK-34451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17819795#comment-17819795 ] Gyula Fora edited comment on FLINK-34451 at 2/22/24 8:12 PM: - I did not mean

[jira] [Commented] (FLINK-34451) [Kubernetes Operator] Job with restarting TaskManagers uses wrong/misleading fallback approach

[ https://issues.apache.org/jira/browse/FLINK-34451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17819795#comment-17819795 ] Gyula Fora commented on FLINK-34451: I did not mean to turn off HA but only to reduce the replicas

[jira] [Commented] (FLINK-34451) [Kubernetes Operator] Job with restarting TaskManagers uses wrong/misleading fallback approach

[ https://issues.apache.org/jira/browse/FLINK-34451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17819783#comment-17819783 ] Gyula Fora commented on FLINK-34451: Could this be related to the the Jobmanager HA? Instead of 2

[jira] [Commented] (FLINK-34451) [Kubernetes Operator] Job with restarting TaskManagers uses wrong/misleading fallback approach

[ https://issues.apache.org/jira/browse/FLINK-34451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17819567#comment-17819567 ] Gyula Fora commented on FLINK-34451: I am only asking because there have been fixes / improvements

[jira] [Commented] (FLINK-34451) [Kubernetes Operator] Job with restarting TaskManagers uses wrong/misleading fallback approach

[ https://issues.apache.org/jira/browse/FLINK-34451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17819564#comment-17819564 ] Gyula Fora commented on FLINK-34451: Which 1.18 version are you using? I have only tried to repro

[jira] (FLINK-34451) [Kubernetes Operator] Job with restarting TaskManagers uses wrong/misleading fallback approach

[ https://issues.apache.org/jira/browse/FLINK-34451 ] Gyula Fora deleted comment on FLINK-34451: was (Author: gyfora): [~alexdchoffer] so, just to confirm: This issue doesn't occur with Flink 1.18? (even with the adaptive scheduler) >

[jira] [Commented] (FLINK-34451) [Kubernetes Operator] Job with restarting TaskManagers uses wrong/misleading fallback approach

[ https://issues.apache.org/jira/browse/FLINK-34451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17819563#comment-17819563 ] Gyula Fora commented on FLINK-34451: [~alexdchoffer] so, just to confirm: This issue doesn't occur

[jira] [Closed] (FLINK-34438) Kubernetes Operator doesn't wait for TaskManager deletion in native mode

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

[jira] [Closed] (FLINK-34213) Consider using accumulated busy time instead of busyMsPerSecond

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

[jira] [Closed] (FLINK-34266) Output ratios should be computed over the whole metric window instead of averaged

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

[jira] [Assigned] (FLINK-33244) Not Able To Pass the Configuration On Flink Session

[ https://issues.apache.org/jira/browse/FLINK-33244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora reassigned FLINK-33244: -- Assignee: Zhenqiu Huang > Not Able To Pass the Configuration On Flink Session >

[jira] [Assigned] (FLINK-28645) Clean up logging in FlinkService / Reconciler

[ https://issues.apache.org/jira/browse/FLINK-28645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora reassigned FLINK-28645: -- Assignee: Zhenqiu Huang > Clean up logging in FlinkService / Reconciler >

[jira] [Commented] (FLINK-34451) [Kubernetes Operator] Job with restarting TaskManagers uses wrong/misleading fallback approach

[ https://issues.apache.org/jira/browse/FLINK-34451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17818126#comment-17818126 ] Gyula Fora commented on FLINK-34451: Before we can investigate the root cause it would be great to

[jira] [Closed] (FLINK-34439) Move chown operations to COPY commands in Dockerfile

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

[jira] [Assigned] (FLINK-34439) Move chown operations to COPY commands in Dockerfile

[ https://issues.apache.org/jira/browse/FLINK-34439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora reassigned FLINK-34439: -- Assignee: Mate Czagany > Move chown operations to COPY commands in Dockerfile >

[jira] [Assigned] (FLINK-34438) Kubernetes Operator doesn't wait for TaskManager deletion in native mode

[ https://issues.apache.org/jira/browse/FLINK-34438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora reassigned FLINK-34438: -- Assignee: Mate Czagany > Kubernetes Operator doesn't wait for TaskManager deletion in native

[jira] [Assigned] (FLINK-34213) Consider using accumulated busy time instead of busyMsPerSecond

[ https://issues.apache.org/jira/browse/FLINK-34213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora reassigned FLINK-34213: -- Assignee: Gyula Fora > Consider using accumulated busy time instead of busyMsPerSecond >

[jira] [Updated] (FLINK-31220) Replace Pod with PodTemplateSpec for the pod template properties

[ https://issues.apache.org/jira/browse/FLINK-31220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-31220: --- Release Note: Deprecation warning: We deprecate Pod fields that are not part of the

[jira] [Closed] (FLINK-34398) Validation Error in FlinkSessionJob Savepoint UpgradeMode Configuration

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

[jira] [Closed] (FLINK-31220) Replace Pod with PodTemplateSpec for the pod template properties

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

[jira] [Closed] (FLINK-34311) Do not change min resource requirements when rescaling for adaptive scheduler

[ https://issues.apache.org/jira/browse/FLINK-34311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora closed FLINK-34311. -- Resolution: Fixed merged to main 4342636cdb2c3439389e83cb4fe4366156edfbd7 > Do not change min

[jira] [Assigned] (FLINK-34266) Output ratios should be computed over the whole metric window instead of averaged

[ https://issues.apache.org/jira/browse/FLINK-34266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora reassigned FLINK-34266: -- Assignee: Gyula Fora > Output ratios should be computed over the whole metric window instead

[jira] [Closed] (FLINK-34319) Bump okhttp version to 4.12.0

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

[jira] [Assigned] (FLINK-31220) Replace Pod with PodTemplateSpec for the pod template properties

[ https://issues.apache.org/jira/browse/FLINK-31220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora reassigned FLINK-31220: -- Assignee: Gyula Fora > Replace Pod with PodTemplateSpec for the pod template properties >

[jira] [Commented] (FLINK-34329) ScalingReport format tests fail locally on decimal format

[ https://issues.apache.org/jira/browse/FLINK-34329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17813090#comment-17813090 ] Gyula Fora commented on FLINK-34329: I don't know the reason yet but the test fails constantly on my

[jira] [Comment Edited] (FLINK-34329) ScalingReport format tests fail locally on decimal format

[ https://issues.apache.org/jira/browse/FLINK-34329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17813074#comment-17813074 ] Gyula Fora edited comment on FLINK-34329 at 2/1/24 7:28 AM: cc [~fanrui] 

[jira] [Commented] (FLINK-34329) ScalingReport format tests fail locally on decimal format

[ https://issues.apache.org/jira/browse/FLINK-34329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17813074#comment-17813074 ] Gyula Fora commented on FLINK-34329: cc @fanrui > ScalingReport format tests fail locally on

  1   2   3   4   5   6   7   8   9   10   >