[jira] [Commented] (FLINK-32127) Source busy time is inaccurate in many cases

[ https://issues.apache.org/jira/browse/FLINK-32127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17781296#comment-17781296 ] Maximilian Michels commented on FLINK-32127: A new scaling method has been merged to address

[jira] [Resolved] (FLINK-32991) Some metrics from autoscaler never get registered

[ https://issues.apache.org/jira/browse/FLINK-32991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels resolved FLINK-32991. Resolution: Fixed > Some metrics from autoscaler never get registered >

[jira] [Commented] (FLINK-32992) Recommended parallelism metric is a duplicate of Parallelism metric

[ https://issues.apache.org/jira/browse/FLINK-32992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17760934#comment-17760934 ] Maximilian Michels commented on FLINK-32992: That makes sense. Closing. > Recommended

[jira] [Resolved] (FLINK-32992) Recommended parallelism metric is a duplicate of Parallelism metric

[ https://issues.apache.org/jira/browse/FLINK-32992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels resolved FLINK-32992. Resolution: Not A Problem > Recommended parallelism metric is a duplicate of

[jira] [Created] (FLINK-32992) Recommended parallelism metric is a duplicate of Parallelism metric

Maximilian Michels created FLINK-32992: -- Summary: Recommended parallelism metric is a duplicate of Parallelism metric Key: FLINK-32992 URL: https://issues.apache.org/jira/browse/FLINK-32992

[jira] [Created] (FLINK-32991) Some metrics from autoscaler never get registered

Maximilian Michels created FLINK-32991: -- Summary: Some metrics from autoscaler never get registered Key: FLINK-32991 URL: https://issues.apache.org/jira/browse/FLINK-32991 Project: Flink

[jira] [Resolved] (FLINK-32959) Operator standalone mode throws NoClassDefFoundError

[ https://issues.apache.org/jira/browse/FLINK-32959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels resolved FLINK-32959. Resolution: Not A Problem This is spot-on! The issue is repacking logic on our

[jira] [Assigned] (FLINK-32959) Operator standalone mode throws NoClassDefFoundError

[ https://issues.apache.org/jira/browse/FLINK-32959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels reassigned FLINK-32959: -- Assignee: Maximilian Michels > Operator standalone mode throws

[jira] [Resolved] (FLINK-32903) Add a load simulation example pipeline for canary testing

[ https://issues.apache.org/jira/browse/FLINK-32903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels resolved FLINK-32903. Resolution: Fixed > Add a load simulation example pipeline for canary testing >

[jira] [Created] (FLINK-32960) Logic to log vertex exclusion only once does not work correctly

Maximilian Michels created FLINK-32960: -- Summary: Logic to log vertex exclusion only once does not work correctly Key: FLINK-32960 URL: https://issues.apache.org/jira/browse/FLINK-32960 Project:

[jira] [Commented] (FLINK-32959) Operator standalone mode throws NoClassDefFoundError

[ https://issues.apache.org/jira/browse/FLINK-32959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17759027#comment-17759027 ] Maximilian Michels commented on FLINK-32959: I think I figured out what caused this. We

[jira] [Created] (FLINK-32959) Operator standalone mode throws NoClassDefFoundError

Maximilian Michels created FLINK-32959: -- Summary: Operator standalone mode throws NoClassDefFoundError Key: FLINK-32959 URL: https://issues.apache.org/jira/browse/FLINK-32959 Project: Flink

[jira] [Updated] (FLINK-32127) Source busy time is inaccurate in many cases

[ https://issues.apache.org/jira/browse/FLINK-32127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels updated FLINK-32127: --- Fix Version/s: kubernetes-operator-1.7.0 > Source busy time is inaccurate in many

[jira] [Assigned] (FLINK-32127) Source busy time is inaccurate in many cases

[ https://issues.apache.org/jira/browse/FLINK-32127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels reassigned FLINK-32127: -- Assignee: Maximilian Michels > Source busy time is inaccurate in many cases

[jira] [Created] (FLINK-32903) Add a load simulation example pipeline for canary testing

Maximilian Michels created FLINK-32903: -- Summary: Add a load simulation example pipeline for canary testing Key: FLINK-32903 URL: https://issues.apache.org/jira/browse/FLINK-32903 Project: Flink

[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=17754052#comment-17754052 ] Maximilian Michels commented on FLINK-31827: Shall we close this issue since the originally

[jira] [Commented] (FLINK-32814) Support disabling failed JM shutdown in the operator

[ https://issues.apache.org/jira/browse/FLINK-32814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754043#comment-17754043 ] Maximilian Michels commented on FLINK-32814: Good suggestion [~sap1ens]! However, I agree

[jira] [Updated] (FLINK-32813) Split autoscaler ConfigMap

[ https://issues.apache.org/jira/browse/FLINK-32813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels updated FLINK-32813: --- Affects Version/s: kubernetes-operator-1.6.0 > Split autoscaler ConfigMap >

[jira] [Created] (FLINK-32813) Split autoscaler ConfigMap

Maximilian Michels created FLINK-32813: -- Summary: Split autoscaler ConfigMap Key: FLINK-32813 URL: https://issues.apache.org/jira/browse/FLINK-32813 Project: Flink Issue Type:

[jira] [Updated] (FLINK-32774) Reconciliation for autoscaling overrides gets stuck after cancel-with-savepoint

[ https://issues.apache.org/jira/browse/FLINK-32774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels updated FLINK-32774: --- Fix Version/s: kubernetes-operator-1.6.0 > Reconciliation for autoscaling overrides

[jira] [Created] (FLINK-32774) Reconciliation for autoscaling overrides gets stuck after cancel-with-savepoint

Maximilian Michels created FLINK-32774: -- Summary: Reconciliation for autoscaling overrides gets stuck after cancel-with-savepoint Key: FLINK-32774 URL: https://issues.apache.org/jira/browse/FLINK-32774

[jira] [Updated] (FLINK-32119) Revise source partition skew logic

[ https://issues.apache.org/jira/browse/FLINK-32119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels updated FLINK-32119: --- Fix Version/s: kubernetes-operator-1.6.0 (was:

[jira] [Updated] (FLINK-32120) Add autoscaler config option to disable parallelism key group alignment

[ https://issues.apache.org/jira/browse/FLINK-32120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels updated FLINK-32120: --- Fix Version/s: kubernetes-operator-1.6.0 (was:

[jira] [Updated] (FLINK-32100) Max parallelism is incorrectly calculated with multiple topics

[ https://issues.apache.org/jira/browse/FLINK-32100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels updated FLINK-32100: --- Fix Version/s: (was: kubernetes-operator-1.5.1) > Max parallelism is

[jira] [Updated] (FLINK-31684) Autoscaler metrics are only visible after metric window is full

[ https://issues.apache.org/jira/browse/FLINK-31684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels updated FLINK-31684: --- Fix Version/s: (was: kubernetes-operator-1.5.1) > Autoscaler metrics are only

[jira] [Updated] (FLINK-32102) Aggregate multiple pendingRecords metric per source if present

[ https://issues.apache.org/jira/browse/FLINK-32102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels updated FLINK-32102: --- Fix Version/s: (was: kubernetes-operator-1.5.1) > Aggregate multiple

[jira] [Commented] (FLINK-28046) Annotate SourceFunction as deprecated

[ https://issues.apache.org/jira/browse/FLINK-28046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17745496#comment-17745496 ] Maximilian Michels commented on FLINK-28046: Are there really any major features missing

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

[ https://issues.apache.org/jira/browse/FLINK-32529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels updated FLINK-32529: --- Fix Version/s: kubernetes-operator-1.6.0 > Optional startup probe for JM deployment

[jira] [Commented] (FLINK-32589) Carry over parallelism overrides to prevent users from clearing them on updates

[ https://issues.apache.org/jira/browse/FLINK-32589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17742865#comment-17742865 ] Maximilian Michels commented on FLINK-32589: We handle this in our application stack but I

[jira] [Created] (FLINK-32589) Carry over parallelism overrides to prevent users from clearing them on updates

Maximilian Michels created FLINK-32589: -- Summary: Carry over parallelism overrides to prevent users from clearing them on updates Key: FLINK-32589 URL: https://issues.apache.org/jira/browse/FLINK-32589

[jira] [Updated] (FLINK-32119) Revise source partition skew logic

[ https://issues.apache.org/jira/browse/FLINK-32119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels updated FLINK-32119: --- Description: After choosing the target parallelism for a vertex, we choose a higher

[jira] [Updated] (FLINK-32119) Add option to control source partition skew

[ https://issues.apache.org/jira/browse/FLINK-32119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels updated FLINK-32119: --- Summary: Add option to control source partition skew (was: Disable key group

[jira] [Commented] (FLINK-28853) FLIP-217 Support watermark alignment of source splits

[ https://issues.apache.org/jira/browse/FLINK-28853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17726781#comment-17726781 ] Maximilian Michels commented on FLINK-28853: Documentation is now fixed. See

[jira] [Resolved] (FLINK-31684) Autoscaler metrics are only visible after metric window is full

[ https://issues.apache.org/jira/browse/FLINK-31684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels resolved FLINK-31684. Fix Version/s: kubernetes-operator-1.6.0

[jira] [Commented] (FLINK-32170) Continue metric collection on intermittant job restarts

[ https://issues.apache.org/jira/browse/FLINK-32170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17725789#comment-17725789 ] Maximilian Michels commented on FLINK-32170: Yes, this is the prerequisite. If we kept an

[jira] [Created] (FLINK-32170) Continue metric collection on intermittant job restarts

Maximilian Michels created FLINK-32170: -- Summary: Continue metric collection on intermittant job restarts Key: FLINK-32170 URL: https://issues.apache.org/jira/browse/FLINK-32170 Project: Flink

[jira] [Commented] (FLINK-32127) Source busy time is inaccurate in many cases

[ https://issues.apache.org/jira/browse/FLINK-32127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17725038#comment-17725038 ] Maximilian Michels commented on FLINK-32127: Thanks for raising the issue. I agree that the

[jira] [Commented] (FLINK-32119) Disable key group alignment for determining source parallelism

[ https://issues.apache.org/jira/browse/FLINK-32119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17723475#comment-17723475 ] Maximilian Michels commented on FLINK-32119: True, partition skew is probably worse than key

[jira] [Created] (FLINK-32120) Add autoscaler config option to disable parallelism key group alignment

Maximilian Michels created FLINK-32120: -- Summary: Add autoscaler config option to disable parallelism key group alignment Key: FLINK-32120 URL: https://issues.apache.org/jira/browse/FLINK-32120

[jira] [Updated] (FLINK-32119) Disable key group alignment for determining source parallelism

[ https://issues.apache.org/jira/browse/FLINK-32119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels updated FLINK-32119: --- Description: After choosing the target parallelism for a vertex, we choose a higher

[jira] [Created] (FLINK-32119) Disable key group alignment for determining source parallelism

Maximilian Michels created FLINK-32119: -- Summary: Disable key group alignment for determining source parallelism Key: FLINK-32119 URL: https://issues.apache.org/jira/browse/FLINK-32119 Project:

[jira] [Resolved] (FLINK-32102) Aggregate multiple pendingRecords metric per source if present

[ https://issues.apache.org/jira/browse/FLINK-32102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels resolved FLINK-32102. Resolution: Fixed > Aggregate multiple pendingRecords metric per source if

[jira] [Resolved] (FLINK-32100) Max parallelism is incorrectly calculated with multiple topics

[ https://issues.apache.org/jira/browse/FLINK-32100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels resolved FLINK-32100. Resolution: Fixed > Max parallelism is incorrectly calculated with multiple

[jira] [Updated] (FLINK-32102) Aggregate multiple pendingRecords metric per source if present

[ https://issues.apache.org/jira/browse/FLINK-32102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels updated FLINK-32102: --- Fix Version/s: kubernetes-operator-1.5.1 (was:

[jira] [Updated] (FLINK-32100) Max parallelism is incorrectly calculated with multiple topics

[ https://issues.apache.org/jira/browse/FLINK-32100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels updated FLINK-32100: --- Fix Version/s: kubernetes-operator-1.6.0

[jira] [Updated] (FLINK-32102) Aggregate multiple pendingRecords metric per source if present

[ https://issues.apache.org/jira/browse/FLINK-32102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels updated FLINK-32102: --- Fix Version/s: kubernetes-operator-1.6.0 > Aggregate multiple pendingRecords metric

[jira] [Created] (FLINK-32102) Aggregate multiple pendingRecords metric per source if present

Maximilian Michels created FLINK-32102: -- Summary: Aggregate multiple pendingRecords metric per source if present Key: FLINK-32102 URL: https://issues.apache.org/jira/browse/FLINK-32102 Project:

[jira] [Updated] (FLINK-32100) Max parallelism is incorrectly calculated with multiple topics

[ https://issues.apache.org/jira/browse/FLINK-32100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels updated FLINK-32100: --- Description: So far, we've taken the max number partitions we can find. However,

[jira] [Updated] (FLINK-32100) Max parallelism is incorrectly calculated with multiple topics

[ https://issues.apache.org/jira/browse/FLINK-32100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels updated FLINK-32100: --- Fix Version/s: (was: kubernetes-operator-1.5.0) > Max parallelism is

[jira] [Created] (FLINK-32100) Max parallelism is incorrectly calculated with multiple topics

Maximilian Michels created FLINK-32100: -- Summary: Max parallelism is incorrectly calculated with multiple topics Key: FLINK-32100 URL: https://issues.apache.org/jira/browse/FLINK-32100 Project:

[jira] [Resolved] (FLINK-32061) Resource metric groups are not cleaned up on removal

[ https://issues.apache.org/jira/browse/FLINK-32061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels resolved FLINK-32061. Resolution: Fixed > Resource metric groups are not cleaned up on removal >

[jira] [Resolved] (FLINK-32005) Add a per-deployment error metric to signal about potential issues

[ https://issues.apache.org/jira/browse/FLINK-32005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels resolved FLINK-32005. Resolution: Fixed > Add a per-deployment error metric to signal about potential

[jira] [Created] (FLINK-32061) Resource metric groups are not cleaned up on removal

Maximilian Michels created FLINK-32061: -- Summary: Resource metric groups are not cleaned up on removal Key: FLINK-32061 URL: https://issues.apache.org/jira/browse/FLINK-32061 Project: Flink

[jira] [Created] (FLINK-32005) Add a per-deployment error metric to signal about potential issues

Maximilian Michels created FLINK-32005: -- Summary: Add a per-deployment error metric to signal about potential issues Key: FLINK-32005 URL: https://issues.apache.org/jira/browse/FLINK-32005

[jira] [Assigned] (FLINK-31867) Enforce a minimum number of observations within a metric window

[ https://issues.apache.org/jira/browse/FLINK-31867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels reassigned FLINK-31867: -- Assignee: Maximilian Michels > Enforce a minimum number of observations

[jira] [Created] (FLINK-32002) Revisit autoscaler defaults for next release

Maximilian Michels created FLINK-32002: -- Summary: Revisit autoscaler defaults for next release Key: FLINK-32002 URL: https://issues.apache.org/jira/browse/FLINK-32002 Project: Flink

[jira] [Updated] (FLINK-31867) Enforce a minimum number of observations within a metric window

[ https://issues.apache.org/jira/browse/FLINK-31867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels updated FLINK-31867: --- Fix Version/s: kubernetes-operator-1.5.0 > Enforce a minimum number of observations

[jira] [Closed] (FLINK-31991) Update Autoscaler doc to reflect the changes brought by the new source scaling logic

[ https://issues.apache.org/jira/browse/FLINK-31991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels closed FLINK-31991. -- Fix Version/s: kubernetes-operator-1.5.0 Resolution: Fixed > Update Autoscaler

[jira] [Assigned] (FLINK-31991) Update Autoscaler doc to reflect the changes brought by the new source scaling logic

[ https://issues.apache.org/jira/browse/FLINK-31991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels reassigned FLINK-31991: -- Assignee: Zhanghao Chen (was: Maximilian Michels) > Update Autoscaler doc

[jira] [Assigned] (FLINK-31991) Update Autoscaler doc to reflect the changes brought by the new source scaling logic

[ https://issues.apache.org/jira/browse/FLINK-31991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels reassigned FLINK-31991: -- Assignee: Maximilian Michels > Update Autoscaler doc to reflect the changes

[jira] [Commented] (FLINK-31991) Update Autoscaler doc to reflect the changes brought by the new source scaling logic

[ https://issues.apache.org/jira/browse/FLINK-31991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17718954#comment-17718954 ] Maximilian Michels commented on FLINK-31991: Thanks for raising this issue. > Update

[jira] [Resolved] (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:all-tabpanel ] Maximilian Michels resolved FLINK-30773. Fix Version/s: 1.18.0 Resolution: Fixed Thanks [~Jiangang] and [~gyfora]!

[jira] [Resolved] (FLINK-31866) Autoscaler metric trimming reduces the number of metric observations on recovery

[ https://issues.apache.org/jira/browse/FLINK-31866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels resolved FLINK-31866. Resolution: Fixed > Autoscaler metric trimming reduces the number of metric

[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=17715824#comment-17715824 ] Maximilian Michels commented on FLINK-31924: Could you clarify what is the issue here? The

[jira] [Created] (FLINK-31921) Create a mini cluster based metric collection test

Maximilian Michels created FLINK-31921: -- Summary: Create a mini cluster based metric collection test Key: FLINK-31921 URL: https://issues.apache.org/jira/browse/FLINK-31921 Project: Flink

[jira] [Updated] (FLINK-31920) Flaky Kubernetes operator tests

[ https://issues.apache.org/jira/browse/FLINK-31920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels updated FLINK-31920: --- Summary: Flaky Kubernetes operator tests (was: Flaky tests ) > Flaky Kubernetes

[jira] [Created] (FLINK-31920) Flaky tests

Maximilian Michels created FLINK-31920: -- Summary: Flaky tests Key: FLINK-31920 URL: https://issues.apache.org/jira/browse/FLINK-31920 Project: Flink Issue Type: Bug

[jira] [Updated] (FLINK-31866) Autoscaler metric trimming reduces the number of metric observations on recovery

[ https://issues.apache.org/jira/browse/FLINK-31866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels updated FLINK-31866: --- Summary: Autoscaler metric trimming reduces the number of metric observations on

[jira] [Updated] (FLINK-31866) Autoscaler metric trimming reduces the numbet of metric observations on recovery

[ https://issues.apache.org/jira/browse/FLINK-31866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels updated FLINK-31866: --- Summary: Autoscaler metric trimming reduces the numbet of metric observations on

[jira] [Resolved] (FLINK-31502) Limit the number of concurrent scale operations to reduce cluster churn

[ https://issues.apache.org/jira/browse/FLINK-31502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels resolved FLINK-31502. Resolution: Won't Fix This turned out to not be the main error source. > Limit

[jira] [Created] (FLINK-31867) Enforce a minimum number of observations within a metric window

Maximilian Michels created FLINK-31867: -- Summary: Enforce a minimum number of observations within a metric window Key: FLINK-31867 URL: https://issues.apache.org/jira/browse/FLINK-31867 Project:

[jira] [Updated] (FLINK-31866) Autoscaler metric trimming reduces the numbet of metric observations

[ https://issues.apache.org/jira/browse/FLINK-31866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels updated FLINK-31866: --- Fix Version/s: kubernetes-operator-1.5.0 > Autoscaler metric trimming reduces the

[jira] [Updated] (FLINK-31866) Autoscaler metric trimming reduces the numbet of metric observations

[ https://issues.apache.org/jira/browse/FLINK-31866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels updated FLINK-31866: --- Component/s: Autoscaler Kubernetes Operator > Autoscaler metric

[jira] [Created] (FLINK-31866) Autoscaler metric trimming reduces the numbet of metric observations

Maximilian Michels created FLINK-31866: -- Summary: Autoscaler metric trimming reduces the numbet of metric observations Key: FLINK-31866 URL: https://issues.apache.org/jira/browse/FLINK-31866

[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=17714530#comment-17714530 ] Maximilian Michels commented on FLINK-31827: We hadn't considered that a vertex with chained

[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=17714529#comment-17714529 ] Maximilian Michels commented on FLINK-31827: Great find [~Zhanghao Chen]! This need to be

[jira] [Updated] (FLINK-30920) K8 cluster autoscaler | exclude operator ids from scaler

[ https://issues.apache.org/jira/browse/FLINK-30920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels updated FLINK-30920: --- Fix Version/s: kubernetes-operator-1.5.0 > K8 cluster autoscaler | exclude operator

[jira] [Created] (FLINK-31684) Autoscaler metrics are only visible after metric window is full

Maximilian Michels created FLINK-31684: -- Summary: Autoscaler metrics are only visible after metric window is full Key: FLINK-31684 URL: https://issues.apache.org/jira/browse/FLINK-31684 Project:

[jira] [Created] (FLINK-31502) Limit the number of concurrent scale operations to reduce cluster churn

Maximilian Michels created FLINK-31502: -- Summary: Limit the number of concurrent scale operations to reduce cluster churn Key: FLINK-31502 URL: https://issues.apache.org/jira/browse/FLINK-31502

[jira] [Commented] (FLINK-31135) ConfigMap DataSize went > 1 MB and cluster stopped working

[ https://issues.apache.org/jira/browse/FLINK-31135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17701681#comment-17701681 ] Maximilian Michels commented on FLINK-31135: Oh, just realized this is unrelated to

[jira] [Reopened] (FLINK-31135) ConfigMap DataSize went > 1 MB and cluster stopped working

[ https://issues.apache.org/jira/browse/FLINK-31135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels reopened FLINK-31135: > ConfigMap DataSize went > 1 MB and cluster stopped working >

[jira] [Resolved] (FLINK-31135) ConfigMap DataSize went > 1 MB and cluster stopped working

[ https://issues.apache.org/jira/browse/FLINK-31135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels resolved FLINK-31135. Resolution: Duplicate Closing because this has been resolved already on the main

[jira] [Commented] (FLINK-31135) ConfigMap DataSize went > 1 MB and cluster stopped working

[ https://issues.apache.org/jira/browse/FLINK-31135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17701679#comment-17701679 ] Maximilian Michels commented on FLINK-31135: This has been addressed in FLINK-31345. >

[jira] [Commented] (FLINK-28853) FLIP-217 Support watermark alignment of source splits

[ https://issues.apache.org/jira/browse/FLINK-28853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17699574#comment-17699574 ] Maximilian Michels commented on FLINK-28853: Thanks [~leonard]! I see there was already a

[jira] [Created] (FLINK-31400) Add autoscaler integration for Iceberg source

Maximilian Michels created FLINK-31400: -- Summary: Add autoscaler integration for Iceberg source Key: FLINK-31400 URL: https://issues.apache.org/jira/browse/FLINK-31400 Project: Flink

[jira] [Updated] (FLINK-31400) Add autoscaler integration for Iceberg source

[ https://issues.apache.org/jira/browse/FLINK-31400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels updated FLINK-31400: --- Description: A very critical part in the scaling algorithm is setting the source

[jira] [Resolved] (FLINK-31326) Disabled source scaling breaks downstream scaling if source busyTimeMsPerSecond is 0

[ https://issues.apache.org/jira/browse/FLINK-31326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels resolved FLINK-31326. Fix Version/s: kubernetes-operator-1.5.0 Release Note: Handle new-style and

[jira] [Resolved] (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 ] Maximilian Michels resolved FLINK-30575. Fix Version/s: kubernetes-operator-1.5.0 Resolution: Fixed > Autoscaler

[jira] [Reopened] (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 ] Maximilian Michels reopened FLINK-30575: > Autoscaler doesn't scale down on 0 load > --- >

[jira] [Resolved] (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 ] Maximilian Michels resolved FLINK-30575. Release Note: Ensure vertices with zero incoming records are scaled down

[jira] [Resolved] (FLINK-31299) PendingRecords metric might not be available

[ https://issues.apache.org/jira/browse/FLINK-31299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels resolved FLINK-31299. Release Note: Work around idle Kafka readers not emitting the pendingRecords

[jira] [Updated] (FLINK-31345) Trim autoscaler configMap to not exceed 1mb size limit

[ https://issues.apache.org/jira/browse/FLINK-31345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels updated FLINK-31345: --- Description: When the {{autoscaler-}} ConfigMap which is used to persist scaling

[jira] [Created] (FLINK-31345) Trim autoscaler configMap to not exceed 1mb size limit

Maximilian Michels created FLINK-31345: -- Summary: Trim autoscaler configMap to not exceed 1mb size limit Key: FLINK-31345 URL: https://issues.apache.org/jira/browse/FLINK-31345 Project: Flink

[jira] [Commented] (FLINK-31326) Disabled source scaling breaks downstream scaling if source busyTimeMsPerSecond is 0

[ https://issues.apache.org/jira/browse/FLINK-31326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17696880#comment-17696880 ] Maximilian Michels commented on FLINK-31326: Thanks [~mateczagany] for reporting! You are

[jira] [Assigned] (FLINK-31326) Disabled source scaling breaks downstream scaling if source busyTimeMsPerSecond is 0

[ https://issues.apache.org/jira/browse/FLINK-31326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels reassigned FLINK-31326: -- Assignee: Maximilian Michels > Disabled source scaling breaks downstream

[jira] [Created] (FLINK-31299) PendingRecords metric might not be available

Maximilian Michels created FLINK-31299: -- Summary: PendingRecords metric might not be available Key: FLINK-31299 URL: https://issues.apache.org/jira/browse/FLINK-31299 Project: Flink

[jira] [Assigned] (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 ] Maximilian Michels reassigned FLINK-30575: -- Assignee: Maximilian Michels > Autoscaler doesn't scale down on 0 load >

[jira] [Assigned] (FLINK-30775) Support pluggable reconciler modules

[ https://issues.apache.org/jira/browse/FLINK-30775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels reassigned FLINK-30775: -- Assignee: (was: Maximilian Michels) > Support pluggable reconciler

[jira] [Updated] (FLINK-30776) Move autoscaler code into a separate module and make it pluggable

[ https://issues.apache.org/jira/browse/FLINK-30776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels updated FLINK-30776: --- Fix Version/s: kubernetes-operator-1.4.0 > Move autoscaler code into a separate

[jira] [Resolved] (FLINK-30776) Move autoscaler code into a separate module and make it pluggable

[ https://issues.apache.org/jira/browse/FLINK-30776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maximilian Michels resolved FLINK-30776. Release Note: Allow plugging in custom autoscaler implementations

<    1   2   3   4   5   6   7   8   9   10   >