[jira] [Created] (FLINK-25323) Support side output late data for interval join

chenyuzhi created FLINK-25323: - Summary: Support side output late data for interval join Key: FLINK-25323 URL: https://issues.apache.org/jira/browse/FLINK-25323 Project: Flink Issue Type:

[jira] [Updated] (FLINK-25323) Support side output late data for interval join

[ https://issues.apache.org/jira/browse/FLINK-25323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-25323: -- External issue ID: FLINK-24907 External issue URL:

[jira] [Updated] (FLINK-25323) Support side output late data for interval join

[ https://issues.apache.org/jira/browse/FLINK-25323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-25323: -- External issue ID: (was: FLINK-24907) External issue URL: (was:

[jira] [Updated] (FLINK-29106) value of metric 'idleTimeMsPerSecond' more than 1000

[ https://issues.apache.org/jira/browse/FLINK-29106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-29106: -- Attachment: image-2022-08-25-19-18-52-755.png > value of metric 'idleTimeMsPerSecond' more than 1000

[jira] [Created] (FLINK-29106) value of metric 'idleTimeMsPerSecond' more than 1000

chenyuzhi created FLINK-29106: - Summary: value of metric 'idleTimeMsPerSecond' more than 1000 Key: FLINK-29106 URL: https://issues.apache.org/jira/browse/FLINK-29106 Project: Flink Issue Type:

[jira] [Updated] (FLINK-29106) value of metric 'idleTimeMsPerSecond' more than 1000

[ https://issues.apache.org/jira/browse/FLINK-29106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-29106: -- Description:  As the picture shown below, the value of metric 'idleTimeMsPerSecond' is more than

[jira] [Comment Edited] (FLINK-28852) Closed metrics could be found in metric dashboard from WebUI

[ https://issues.apache.org/jira/browse/FLINK-28852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17590109#comment-17590109 ] chenyuzhi edited comment on FLINK-28852 at 8/31/22 8:23 AM: I'd like to take

[jira] [Updated] (FLINK-28852) Closed metrics could be found in metric dashboard from WebUI

[ https://issues.apache.org/jira/browse/FLINK-28852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-28852: -- Affects Version/s: 1.14.0 Environment: Flink 1.11.3/1.14.0 (was: Flink 1.11.3) > Closed

[jira] [Commented] (FLINK-29195) Expose lastCheckpointId metric

[ https://issues.apache.org/jira/browse/FLINK-29195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600790#comment-17600790 ] chenyuzhi commented on FLINK-29195: --- Thanks for your tips!  We could do get the  latest checkpoint id

[jira] [Comment Edited] (FLINK-29195) Expose lastCheckpointId metric

[ https://issues.apache.org/jira/browse/FLINK-29195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600790#comment-17600790 ] chenyuzhi edited comment on FLINK-29195 at 9/6/22 2:21 PM: --- Thanks for your

[jira] [Commented] (FLINK-29195) Expose lastCheckpointId metric

[ https://issues.apache.org/jira/browse/FLINK-29195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600787#comment-17600787 ] chenyuzhi commented on FLINK-29195: --- [~masteryhx]  > Expose lastCheckpointId metric >

[jira] (FLINK-29195) Expose lastCheckpointId metric

[ https://issues.apache.org/jira/browse/FLINK-29195 ] chenyuzhi deleted comment on FLINK-29195: --- was (Author: stupid_pig): [~masteryhx]  > Expose lastCheckpointId metric > --- > > Key: FLINK-29195 >

[jira] [Comment Edited] (FLINK-28852) Closed metrics could be found in metric dashboard from WebUI

[ https://issues.apache.org/jira/browse/FLINK-28852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17590109#comment-17590109 ] chenyuzhi edited comment on FLINK-28852 at 8/28/22 1:13 PM: I think the

[jira] [Comment Edited] (FLINK-28852) Closed metrics could be found in metric dashboard from WebUI

[ https://issues.apache.org/jira/browse/FLINK-28852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17590109#comment-17590109 ] chenyuzhi edited comment on FLINK-28852 at 8/28/22 1:13 PM: I think the

[jira] [Comment Edited] (FLINK-28852) Closed metrics could be found in metric dashboard from WebUI

[ https://issues.apache.org/jira/browse/FLINK-28852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17590109#comment-17590109 ] chenyuzhi edited comment on FLINK-28852 at 8/28/22 1:12 PM: I think the

[jira] [Comment Edited] (FLINK-28852) Closed metrics could be found in metric dashboard from WebUI

[ https://issues.apache.org/jira/browse/FLINK-28852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17590109#comment-17590109 ] chenyuzhi edited comment on FLINK-28852 at 8/28/22 1:30 PM: I think the

[jira] [Commented] (FLINK-28852) Closed metrics could be found in metric dashboard from WebUI

[ https://issues.apache.org/jira/browse/FLINK-28852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17590109#comment-17590109 ] chenyuzhi commented on FLINK-28852: --- I think the problem comes from *MetricStore.class,* beause it

[jira] [Commented] (FLINK-29387) IntervalJoinITCase.testIntervalJoinSideOutputRightLateData failed with AssertionError

[ https://issues.apache.org/jira/browse/FLINK-29387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17610503#comment-17610503 ] chenyuzhi commented on FLINK-29387: --- I have return testIntervalJoinSideOutputLeftLateData() and 

[jira] [Comment Edited] (FLINK-29387) IntervalJoinITCase.testIntervalJoinSideOutputRightLateData failed with AssertionError

[ https://issues.apache.org/jira/browse/FLINK-29387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17610503#comment-17610503 ] chenyuzhi edited comment on FLINK-29387 at 9/28/22 11:22 AM: - I have re-run

[jira] [Commented] (FLINK-29387) IntervalJoinITCase.testIntervalJoinSideOutputRightLateData failed with AssertionError

[ https://issues.apache.org/jira/browse/FLINK-29387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17618716#comment-17618716 ] chenyuzhi commented on FLINK-29387: --- [~chesnay]  Well, how could I  run the unit test in parallel

[jira] [Updated] (FLINK-29195) Expose lastCheckpointId metric

[ https://issues.apache.org/jira/browse/FLINK-29195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-29195: -- Component/s: Runtime / Metrics > Expose lastCheckpointId metric > --- >

[jira] [Updated] (FLINK-29195) Expose lastCheckpointId metric

[ https://issues.apache.org/jira/browse/FLINK-29195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-29195: -- Description: May be we could expose  > Expose lastCheckpointId metric >

[jira] [Created] (FLINK-29195) Expose lastCheckpointId metric

chenyuzhi created FLINK-29195: - Summary: Expose lastCheckpointId metric Key: FLINK-29195 URL: https://issues.apache.org/jira/browse/FLINK-29195 Project: Flink Issue Type: New Feature

[jira] [Updated] (FLINK-29195) Expose lastCheckpointId metric

[ https://issues.apache.org/jira/browse/FLINK-29195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-29195: -- Description:  May be we could expose the lastCheckpointId metric. With this metric, we could monitor

[jira] [Updated] (FLINK-29195) Expose lastCheckpointId metric

[ https://issues.apache.org/jira/browse/FLINK-29195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-29195: -- Description:  May be we could expose the lastCheckpointId metric. With this metric, we could monitor

[jira] [Comment Edited] (FLINK-29195) Expose lastCheckpointId metric

[ https://issues.apache.org/jira/browse/FLINK-29195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600335#comment-17600335 ] chenyuzhi edited comment on FLINK-29195 at 9/5/22 11:25 AM: I'd like to take

[jira] [Commented] (FLINK-29195) Expose lastCheckpointId metric

[ https://issues.apache.org/jira/browse/FLINK-29195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17600335#comment-17600335 ] chenyuzhi commented on FLINK-29195: --- I'd like to take this tickent > Expose lastCheckpointId metric

[jira] [Updated] (FLINK-29195) Expose lastCheckpointId metric

[ https://issues.apache.org/jira/browse/FLINK-29195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-29195: -- Component/s: Runtime / Checkpointing > Expose lastCheckpointId metric >

[jira] [Created] (FLINK-28852) Closed metric group could be found in metric dashboard from WebUI

chenyuzhi created FLINK-28852: - Summary: Closed metric group could be found in metric dashboard from WebUI Key: FLINK-28852 URL: https://issues.apache.org/jira/browse/FLINK-28852 Project: Flink

[jira] [Updated] (FLINK-28852) Closed metrics could be found in metric dashboard from WebUI

[ https://issues.apache.org/jira/browse/FLINK-28852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-28852: -- Summary: Closed metrics could be found in metric dashboard from WebUI (was: Closed metric group

[jira] [Updated] (FLINK-28852) Closed metrics could be found in metric dashboard from WebUI

[ https://issues.apache.org/jira/browse/FLINK-28852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-28852: -- Description: When I close  metric group, the related metrics would be unregistered from

[jira] [Created] (FLINK-30818) add metrics to measure the count of window

chenyuzhi created FLINK-30818: - Summary: add metrics to measure the count of window Key: FLINK-30818 URL: https://issues.apache.org/jira/browse/FLINK-30818 Project: Flink Issue Type: Improvement

[jira] [Updated] (FLINK-30818) add metrics to measure the count of window

[ https://issues.apache.org/jira/browse/FLINK-30818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-30818: -- Description: When recovering a job which using window operator,  taskmanager will need more

[jira] [Commented] (FLINK-29387) IntervalJoinITCase.testIntervalJoinSideOutputRightLateData failed with AssertionError

[ https://issues.apache.org/jira/browse/FLINK-29387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17632623#comment-17632623 ] chenyuzhi commented on FLINK-29387: --- [~mapohl] [~hxbks2ks]  I think the problem may be the watermark

[jira] [Updated] (FLINK-30987) output source exception for SocketStreamIterator

[ https://issues.apache.org/jira/browse/FLINK-30987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-30987: -- Description: Sometime we could meet some error when using

[jira] [Created] (FLINK-30987) output source exception for SocketStreamIterator

chenyuzhi created FLINK-30987: - Summary: output source exception for SocketStreamIterator Key: FLINK-30987 URL: https://issues.apache.org/jira/browse/FLINK-30987 Project: Flink Issue Type:

[jira] [Updated] (FLINK-32636) Promethues metric exporter expose stopped job metric

[ https://issues.apache.org/jira/browse/FLINK-32636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-32636: -- Attachment: image-2023-07-20-17-04-53-069.png > Promethues metric exporter expose stopped job metric

[jira] [Updated] (FLINK-32636) Promethues metric exporter expose stopped job metric

[ https://issues.apache.org/jira/browse/FLINK-32636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-32636: -- Attachment: image-2023-07-20-17-04-18-489.png > Promethues metric exporter expose stopped job metric

[jira] [Created] (FLINK-32636) Promethues metric exporter expose stopped job metric

chenyuzhi created FLINK-32636: - Summary: Promethues metric exporter expose stopped job metric Key: FLINK-32636 URL: https://issues.apache.org/jira/browse/FLINK-32636 Project: Flink Issue Type:

[jira] [Updated] (FLINK-32636) Promethues metric exporter expose stopped job metric

[ https://issues.apache.org/jira/browse/FLINK-32636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-32636: -- Description: Firstly, I have submitted two jobs(let's say jobA/jobB ) to flink session. When I

[jira] [Updated] (FLINK-32649) Mismatch label and value for prometheus reporter

[ https://issues.apache.org/jira/browse/FLINK-32649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-32649: -- Component/s: Runtime / Metrics > Mismatch label and value for prometheus reporter >

[jira] [Updated] (FLINK-32649) Mismatch label and value for prometheus reporter

[ https://issues.apache.org/jira/browse/FLINK-32649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-32649: -- Description: When runing unit test 

[jira] [Created] (FLINK-32649) Mismatch label and value for prometheus reporter

chenyuzhi created FLINK-32649: - Summary: Mismatch label and value for prometheus reporter Key: FLINK-32649 URL: https://issues.apache.org/jira/browse/FLINK-32649 Project: Flink Issue Type: Bug

[jira] [Updated] (FLINK-32669) Support range-port for taskmanager data port

[ https://issues.apache.org/jira/browse/FLINK-32669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-32669: -- Description: We can setup range-port for taskmanager rpc port to avoid occupying an unexpected

[jira] [Created] (FLINK-32669) Support port-range for taskmanager data port

chenyuzhi created FLINK-32669: - Summary: Support port-range for taskmanager data port Key: FLINK-32669 URL: https://issues.apache.org/jira/browse/FLINK-32669 Project: Flink Issue Type:

[jira] [Updated] (FLINK-32669) Support range-port for taskmanager data port

[ https://issues.apache.org/jira/browse/FLINK-32669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-32669: -- Description: We can setup range-port for taskmanager rpc port to avoid occupying an unexpected

[jira] [Updated] (FLINK-32669) Support port-range for taskmanager data port

[ https://issues.apache.org/jira/browse/FLINK-32669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-32669: -- Description: We can setup range-port for taskmanager rpc port to avoid occupying an unexpected

[jira] [Updated] (FLINK-32669) Support port-range for taskmanager data port

[ https://issues.apache.org/jira/browse/FLINK-32669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-32669: -- Description: We can setup range-port for taskmanager rpc port to avoid occupying an unexpected

[jira] [Updated] (FLINK-32669) Support range-port for taskmanager data port

[ https://issues.apache.org/jira/browse/FLINK-32669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-32669: -- Summary: Support range-port for taskmanager data port (was: Support port-range for taskmanager data

[jira] [Commented] (FLINK-32669) Support range-port for taskmanager data port

[ https://issues.apache.org/jira/browse/FLINK-32669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17746903#comment-17746903 ] chenyuzhi commented on FLINK-32669: --- In our hadoop cluster, our datanode service would  restarts to

[jira] [Created] (FLINK-34008) Taskmanager blocked with deserialization when starting

chenyuzhi created FLINK-34008: - Summary: Taskmanager blocked with deserialization when starting Key: FLINK-34008 URL: https://issues.apache.org/jira/browse/FLINK-34008 Project: Flink Issue Type:

[jira] [Updated] (FLINK-35192) operator oom

[ https://issues.apache.org/jira/browse/FLINK-35192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-35192: -- Attachment: screenshot-2.png > operator oom > > > Key: FLINK-35192 >

[jira] [Updated] (FLINK-35192) operator oom

[ https://issues.apache.org/jira/browse/FLINK-35192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-35192: -- Attachment: screenshot-1.png > operator oom > > > Key: FLINK-35192 >

[jira] [Updated] (FLINK-35192) operator oom

[ https://issues.apache.org/jira/browse/FLINK-35192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-35192: -- Description: The kubernetest operator docker process was killed by kernel cause out of memory(the

[jira] [Created] (FLINK-35192) operator oom

chenyuzhi created FLINK-35192: - Summary: operator oom Key: FLINK-35192 URL: https://issues.apache.org/jira/browse/FLINK-35192 Project: Flink Issue Type: Bug Components: Kubernetes

[jira] [Comment Edited] (FLINK-35192) operator oom

[ https://issues.apache.org/jira/browse/FLINK-35192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17839545#comment-17839545 ] chenyuzhi edited comment on FLINK-35192 at 4/22/24 8:18 AM: the yaml spec:

[jira] [Updated] (FLINK-35192) operator oom

[ https://issues.apache.org/jira/browse/FLINK-35192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-35192: -- Description: The kubernetest operator docker process was killed by kernel cause out of memory(the

[jira] [Comment Edited] (FLINK-35192) operator oom

[ https://issues.apache.org/jira/browse/FLINK-35192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17839545#comment-17839545 ] chenyuzhi edited comment on FLINK-35192 at 4/22/24 8:21 AM: the yaml spec:

[jira] [Commented] (FLINK-35192) operator oom

[ https://issues.apache.org/jira/browse/FLINK-35192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17839546#comment-17839546 ] chenyuzhi commented on FLINK-35192: --- Could you help to have look at this operator problem when you

[jira] [Commented] (FLINK-35192) operator oom

[ https://issues.apache.org/jira/browse/FLINK-35192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17839545#comment-17839545 ] chenyuzhi commented on FLINK-35192: --- the yaml spec: {code:yaml} apiVersion: apps/v1 kind: Deployment

[jira] [Updated] (FLINK-35192) operator oom

[ https://issues.apache.org/jira/browse/FLINK-35192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-35192: -- Description: The kubernetest operator docker process was killed by kernel cause out of memory(the

[jira] [Comment Edited] (FLINK-35192) operator oom

[ https://issues.apache.org/jira/browse/FLINK-35192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842312#comment-17842312 ] chenyuzhi edited comment on FLINK-35192 at 4/30/24 9:17 AM:   The op image

[jira] [Comment Edited] (FLINK-35192) operator oom

[ https://issues.apache.org/jira/browse/FLINK-35192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842312#comment-17842312 ] chenyuzhi edited comment on FLINK-35192 at 4/30/24 9:19 AM:   The op image

[jira] [Commented] (FLINK-35192) operator oom

[ https://issues.apache.org/jira/browse/FLINK-35192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842312#comment-17842312 ] chenyuzhi commented on FLINK-35192: ---   The op image we use is to modify the basic image of the

[jira] [Comment Edited] (FLINK-35192) operator oom

[ https://issues.apache.org/jira/browse/FLINK-35192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842312#comment-17842312 ] chenyuzhi edited comment on FLINK-35192 at 4/30/24 9:26 AM:   The op image

[jira] [Updated] (FLINK-35192) operator oom

[ https://issues.apache.org/jira/browse/FLINK-35192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-35192: -- Attachment: image-2024-04-30-16-47-07-289.png > operator oom > > > Key:

[jira] [Updated] (FLINK-35192) operator oom

[ https://issues.apache.org/jira/browse/FLINK-35192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-35192: -- Attachment: image-2024-04-30-17-11-24-974.png > operator oom > > > Key:

[jira] [Comment Edited] (FLINK-35192) operator oom

[ https://issues.apache.org/jira/browse/FLINK-35192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842312#comment-17842312 ] chenyuzhi edited comment on FLINK-35192 at 4/30/24 9:24 AM:   The op image

[jira] [Comment Edited] (FLINK-35192) operator oom

[ https://issues.apache.org/jira/browse/FLINK-35192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842312#comment-17842312 ] chenyuzhi edited comment on FLINK-35192 at 4/30/24 12:44 PM: -   The op

[jira] [Commented] (FLINK-35192) operator oom

[ https://issues.apache.org/jira/browse/FLINK-35192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842366#comment-17842366 ] chenyuzhi commented on FLINK-35192: --- It's probably not that the images aren't broken, but that they're

[jira] [Updated] (FLINK-35192) Kubernetes operator oom

[ https://issues.apache.org/jira/browse/FLINK-35192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenyuzhi updated FLINK-35192: -- Attachment: screenshot-4.png > Kubernetes operator oom > --- > >

[jira] [Commented] (FLINK-35192) Kubernetes operator oom

[ https://issues.apache.org/jira/browse/FLINK-35192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844545#comment-17844545 ] chenyuzhi commented on FLINK-35192: --- In our environment, the operator has been running for more than

[jira] [Comment Edited] (FLINK-35192) Kubernetes operator oom

[ https://issues.apache.org/jira/browse/FLINK-35192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844545#comment-17844545 ] chenyuzhi edited comment on FLINK-35192 at 5/8/24 6:04 AM: --- In our

[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=17824029#comment-17824029 ] chenyuzhi edited comment on FLINK-34576 at 3/6/24 2:26 PM: --- According to this

[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=17824029#comment-17824029 ] chenyuzhi edited comment on FLINK-34576 at 3/6/24 2:25 PM: --- According to this

[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=17824029#comment-17824029 ] chenyuzhi commented on FLINK-34576: --- According to this JOSDK [

[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=17824288#comment-17824288 ] chenyuzhi commented on FLINK-34576: --- "Not sure how to repro this in a test easily, you could try

[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=17824324#comment-17824324 ] chenyuzhi commented on FLINK-34576: --- Analyzing from the log of the operator above, when the operator

[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=17824324#comment-17824324 ] chenyuzhi edited comment on FLINK-34576 at 3/7/24 9:05 AM: --- Analyzing from the

[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=17823864#comment-17823864 ] chenyuzhi commented on FLINK-34576: --- I have check our operaotr's log， got some error log： {code:java}

[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 ] chenyuzhi updated FLINK-34576: -- Description: The HA mode of flink-kubernetes-operator is being used. When one of the pods of

[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 ] chenyuzhi updated FLINK-34576: -- Description: The HA mode of flink-kubernetes-operator is being used. When one of the pods of

[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 ] chenyuzhi updated FLINK-34576: -- Description: The HA mode of flink-kubernetes-operator is being used. When one of the pods of

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

chenyuzhi created FLINK-34576: - Summary: Flink deployment keep staying at RECONCILING/STABLE status Key: FLINK-34576 URL: https://issues.apache.org/jira/browse/FLINK-34576 Project: Flink Issue

[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=17823574#comment-17823574 ] chenyuzhi commented on FLINK-34576: --- [~gyfora]    Hello, I'm sorry to bother you. Could you help to

[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=17823663#comment-17823663 ] chenyuzhi commented on FLINK-34576: --- Thanks for the reply. 1.  Is there a way to somehow repro this

[jira] [Commented] (FLINK-35192) Kubernetes operator oom

[ https://issues.apache.org/jira/browse/FLINK-35192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851055#comment-17851055 ] chenyuzhi commented on FLINK-35192: --- I've picked up the relevant pr and running it in my local