[jira] [Updated] (FLINK-14411) OrcTableSource read error

[ https://issues.apache.org/jira/browse/FLINK-14411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 updated FLINK-14411: Description: Hello, when I used BatchTableEnvironment to run a query on OrcTableSource, I got a

[jira] [Created] (FLINK-14411) OrcTableSource read error

zlzhang0122 created FLINK-14411: --- Summary: OrcTableSource read error Key: FLINK-14411 URL: https://issues.apache.org/jira/browse/FLINK-14411 Project: Flink Issue Type: Bug Affects

[jira] [Commented] (FLINK-19594) SubTasks start index don't unified and may confuse users

[ https://issues.apache.org/jira/browse/FLINK-19594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17213687#comment-17213687 ] zlzhang0122 commented on FLINK-19594: - also i have found Watermarks page has the same problem and

[jira] [Created] (FLINK-19594) SubTasks start index don't unified and may confuse users

zlzhang0122 created FLINK-19594: --- Summary: SubTasks start index don't unified and may confuse users Key: FLINK-19594 URL: https://issues.apache.org/jira/browse/FLINK-19594 Project: Flink Issue

[jira] [Comment Edited] (FLINK-19594) SubTasks start index don't unified and may confuse users

[ https://issues.apache.org/jira/browse/FLINK-19594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17212816#comment-17212816 ] zlzhang0122 edited comment on FLINK-19594 at 10/13/20, 3:44 AM:

[jira] [Comment Edited] (FLINK-19594) SubTasks start index don't unified and may confuse users

[ https://issues.apache.org/jira/browse/FLINK-19594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17212816#comment-17212816 ] zlzhang0122 edited comment on FLINK-19594 at 10/13/20, 3:44 AM:

[jira] [Commented] (FLINK-19594) SubTasks start index don't unified and may confuse users

[ https://issues.apache.org/jira/browse/FLINK-19594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17212816#comment-17212816 ] zlzhang0122 commented on FLINK-19594: - [^BackPresures.png]   [^Checkpoints.png]  

[jira] [Updated] (FLINK-19594) SubTasks start index don't unified and may confuse users

[ https://issues.apache.org/jira/browse/FLINK-19594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 updated FLINK-19594: Description: In flink web ui page, subTasks index start from 0 in SubTasks tab while in

[jira] [Commented] (FLINK-20735) Support configurable log level

[ https://issues.apache.org/jira/browse/FLINK-20735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17255876#comment-17255876 ] zlzhang0122 commented on FLINK-20735: - [~trohrmann] Ah, I'm suggesting to make the log4j properties

[jira] [Created] (FLINK-20800) HadoopViewFileSystemTruncateTest failure caused by AssumptionViolatedException

zlzhang0122 created FLINK-20800: --- Summary: HadoopViewFileSystemTruncateTest failure caused by AssumptionViolatedException Key: FLINK-20800 URL: https://issues.apache.org/jira/browse/FLINK-20800

[jira] [Commented] (FLINK-20800) HadoopViewFileSystemTruncateTest failure caused by AssumptionViolatedException

[ https://issues.apache.org/jira/browse/FLINK-20800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17255878#comment-17255878 ] zlzhang0122 commented on FLINK-20800: - I think this problem can be solved by add a config to

[jira] [Updated] (FLINK-20891) SystemResourcesCounterTest may caused endless loop when some error occured

[ https://issues.apache.org/jira/browse/FLINK-20891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 updated FLINK-20891: Description: When the function run() in  class SystemResourcesCounter  come across Throwable

[jira] [Commented] (FLINK-20891) SystemResourcesCounterTest may caused endless loop when some error occured

[ https://issues.apache.org/jira/browse/FLINK-20891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17260494#comment-17260494 ] zlzhang0122 commented on FLINK-20891: - [INFO] Running

[jira] [Updated] (FLINK-20891) SystemResourcesCounterTest may caused endless loop when some error occured

[ https://issues.apache.org/jira/browse/FLINK-20891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 updated FLINK-20891: Description: When the function run() in  class SystemResourcesCounter  come across Throwable

[jira] [Updated] (FLINK-20891) SystemResourcesCounterTest may caused endless loop when some error occured

[ https://issues.apache.org/jira/browse/FLINK-20891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 updated FLINK-20891: Description: When the function run() in  class SystemResourcesCounter  come across Throwable

[jira] [Created] (FLINK-20891) SystemResourcesCounterTest may caused endless loop when some error occured

zlzhang0122 created FLINK-20891: --- Summary: SystemResourcesCounterTest may caused endless loop when some error occured Key: FLINK-20891 URL: https://issues.apache.org/jira/browse/FLINK-20891 Project:

[jira] [Commented] (FLINK-20367) Show the in-use config of job to users

[ https://issues.apache.org/jira/browse/FLINK-20367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17240719#comment-17240719 ] zlzhang0122 commented on FLINK-20367: - ah, I just think that we can give a runtime configuration for

[jira] [Updated] (FLINK-20424) The percent of acknowledged checkpoint seems incorrect

[ https://issues.apache.org/jira/browse/FLINK-20424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 updated FLINK-20424: Description: As the picture below, the percent of acknowledged checkpoint seems incorrect.I

[jira] [Created] (FLINK-20424) The percent of acknowledged checkpoint seems incorrect

zlzhang0122 created FLINK-20424: --- Summary: The percent of acknowledged checkpoint seems incorrect Key: FLINK-20424 URL: https://issues.apache.org/jira/browse/FLINK-20424 Project: Flink Issue

[jira] [Created] (FLINK-20367) Show the in-use config of job to users

zlzhang0122 created FLINK-20367: --- Summary: Show the in-use config of job to users Key: FLINK-20367 URL: https://issues.apache.org/jira/browse/FLINK-20367 Project: Flink Issue Type: Improvement

[jira] [Commented] (FLINK-20473) when get metrics option, its hard to see the full name unless u choosed

[ https://issues.apache.org/jira/browse/FLINK-20473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17245085#comment-17245085 ] zlzhang0122 commented on FLINK-20473: - If necessary, can I take this and fix it? > when get metrics

[jira] [Closed] (FLINK-14411) OrcTableSource read error

[ https://issues.apache.org/jira/browse/FLINK-14411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 closed FLINK-14411. --- Resolution: Cannot Reproduce > OrcTableSource read error > - > >

[jira] [Commented] (FLINK-14411) OrcTableSource read error

[ https://issues.apache.org/jira/browse/FLINK-14411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17243655#comment-17243655 ] zlzhang0122 commented on FLINK-14411: - I rerun this code in flink 1.11 and got no exception, i think

[jira] [Commented] (FLINK-20473) when get metrics option, its hard to see the full name unless u choosed

[ https://issues.apache.org/jira/browse/FLINK-20473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17243764#comment-17243764 ] zlzhang0122 commented on FLINK-20473: - +1. I think maybe when cursor hover on the text and display

[jira] [Comment Edited] (FLINK-20618) Some of the source operator subtasks will stuck when flink job in critical backpressure

[ https://issues.apache.org/jira/browse/FLINK-20618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17250917#comment-17250917 ] zlzhang0122 edited comment on FLINK-20618 at 12/17/20, 9:17 AM: Sure,

[jira] [Comment Edited] (FLINK-20618) Some of the source operator subtasks will stuck when flink job in critical backpressure

[ https://issues.apache.org/jira/browse/FLINK-20618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17250917#comment-17250917 ] zlzhang0122 edited comment on FLINK-20618 at 12/17/20, 9:14 AM: Sure,

[jira] [Comment Edited] (FLINK-20618) Some of the source operator subtasks will stuck when flink job in critical backpressure

[ https://issues.apache.org/jira/browse/FLINK-20618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17251450#comment-17251450 ] zlzhang0122 edited comment on FLINK-20618 at 12/18/20, 2:28 AM: 1. I

[jira] [Comment Edited] (FLINK-20618) Some of the source operator subtasks will stuck when flink job in critical backpressure

[ https://issues.apache.org/jira/browse/FLINK-20618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17251450#comment-17251450 ] zlzhang0122 edited comment on FLINK-20618 at 12/18/20, 2:27 AM: I have

[jira] [Commented] (FLINK-20618) Some of the source operator subtasks will stuck when flink job in critical backpressure

[ https://issues.apache.org/jira/browse/FLINK-20618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17251450#comment-17251450 ] zlzhang0122 commented on FLINK-20618: - # I have tried this job on the version of 1.10.0 and 1.11.1,

[jira] [Updated] (FLINK-20618) Some of the source operator subtasks will stuck when flink job in critical backpressure

[ https://issues.apache.org/jira/browse/FLINK-20618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 updated FLINK-20618: Attachment: stuck_node.txt > Some of the source operator subtasks will stuck when flink job in

[jira] [Updated] (FLINK-20618) Some of the source operator subtasks will stuck when flink job in critical backpressure

[ https://issues.apache.org/jira/browse/FLINK-20618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 updated FLINK-20618: Attachment: stuck_node_downstream.txt > Some of the source operator subtasks will stuck when

[jira] [Comment Edited] (FLINK-20618) Some of the source operator subtasks will stuck when flink job in critical backpressure

[ https://issues.apache.org/jira/browse/FLINK-20618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17251450#comment-17251450 ] zlzhang0122 edited comment on FLINK-20618 at 12/18/20, 2:38 AM: 1. I

[jira] [Comment Edited] (FLINK-20618) Some of the source operator subtasks will stuck when flink job in critical backpressure

[ https://issues.apache.org/jira/browse/FLINK-20618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17250917#comment-17250917 ] zlzhang0122 edited comment on FLINK-20618 at 12/18/20, 2:49 AM: Sure,

[jira] [Created] (FLINK-20571) Add dynamic open/close LatencyMarksEmitter to support online debug and monitoring

zlzhang0122 created FLINK-20571: --- Summary: Add dynamic open/close LatencyMarksEmitter to support online debug and monitoring Key: FLINK-20571 URL: https://issues.apache.org/jira/browse/FLINK-20571

[jira] [Updated] (FLINK-20571) Add dynamic open/close LatencyMarksEmitter to support online debug and monitoring

[ https://issues.apache.org/jira/browse/FLINK-20571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 updated FLINK-20571: Description: Now, flink has provided latency metrics to monitor the latency, but this function

[jira] [Updated] (FLINK-20571) Add dynamic open/close LatencyMarksEmitter to support online debug and monitoring

[ https://issues.apache.org/jira/browse/FLINK-20571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 updated FLINK-20571: Description: Now, flink has provided latency metrics to monitor the latency, but this function

[jira] [Updated] (FLINK-20571) Add dynamic open/close LatencyMarksEmitter to support online debug and monitoring

[ https://issues.apache.org/jira/browse/FLINK-20571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 updated FLINK-20571: Description: Now, flink has provided latency metrics to monitor the latency, but this function

[jira] [Updated] (FLINK-20571) Add dynamic open/close LatencyMarksEmitter to support online debug and monitoring

[ https://issues.apache.org/jira/browse/FLINK-20571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 updated FLINK-20571: Description: Now, flink has provided latency metrics to monitor the latency, but this function

[jira] [Comment Edited] (FLINK-20618) Some of the source operator subtasks will stuck when flink job in critical backpressure

[ https://issues.apache.org/jira/browse/FLINK-20618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17252574#comment-17252574 ] zlzhang0122 edited comment on FLINK-20618 at 12/21/20, 2:26 AM: Thanks

[jira] [Commented] (FLINK-20618) Some of the source operator subtasks will stuck when flink job in critical backpressure

[ https://issues.apache.org/jira/browse/FLINK-20618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17252685#comment-17252685 ] zlzhang0122 commented on FLINK-20618: - Ok, the network engineer is checking the network of the old

[jira] [Commented] (FLINK-20618) Some of the source operator subtasks will stuck when flink job in critical backpressure

[ https://issues.apache.org/jira/browse/FLINK-20618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17252574#comment-17252574 ] zlzhang0122 commented on FLINK-20618: - Thanks for your reply [~pnowojski]. I have the same confusion

[jira] [Created] (FLINK-20735) Support configurable log level

zlzhang0122 created FLINK-20735: --- Summary: Support configurable log level Key: FLINK-20735 URL: https://issues.apache.org/jira/browse/FLINK-20735 Project: Flink Issue Type: Improvement

[jira] [Updated] (FLINK-20618) Some of the source operator subtasks will stuck when flink job in critical backpressure

[ https://issues.apache.org/jira/browse/FLINK-20618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 updated FLINK-20618: Attachment: 2020-12-17 10-51-42 的屏幕截图.png > Some of the source operator subtasks will stuck when

[jira] [Updated] (FLINK-20618) Some of the source operator subtasks will stuck when flink job in critical backpressure

[ https://issues.apache.org/jira/browse/FLINK-20618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 updated FLINK-20618: Attachment: 2020-12-17 11-10-06 的屏幕截图.png > Some of the source operator subtasks will stuck when

[jira] [Updated] (FLINK-20618) Some of the source operator subtasks will stuck when flink job in critical backpressure

[ https://issues.apache.org/jira/browse/FLINK-20618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 updated FLINK-20618: Attachment: (was: 2020-12-17 10-51-42 的屏幕截图.png) > Some of the source operator subtasks will

[jira] [Commented] (FLINK-20618) Some of the source operator subtasks will stuck when flink job in critical backpressure

[ https://issues.apache.org/jira/browse/FLINK-20618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17250770#comment-17250770 ] zlzhang0122 commented on FLINK-20618: - > the other task run well > > [~roman_khachatryan]  Could

[jira] [Comment Edited] (FLINK-20618) Some of the source operator subtasks will stuck when flink job in critical backpressure

[ https://issues.apache.org/jira/browse/FLINK-20618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17250770#comment-17250770 ] zlzhang0122 edited comment on FLINK-20618 at 12/17/20, 3:21 AM: > the

[jira] [Comment Edited] (FLINK-20618) Some of the source operator subtasks will stuck when flink job in critical backpressure

[ https://issues.apache.org/jira/browse/FLINK-20618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17250770#comment-17250770 ] zlzhang0122 edited comment on FLINK-20618 at 12/17/20, 3:21 AM: > the

[jira] [Comment Edited] (FLINK-20618) Some of the source operator subtasks will stuck when flink job in critical backpressure

[ https://issues.apache.org/jira/browse/FLINK-20618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17250770#comment-17250770 ] zlzhang0122 edited comment on FLINK-20618 at 12/17/20, 3:24 AM: > the

[jira] [Updated] (FLINK-20618) Some of the source operator subtasks will stuck when flink job in critical backpressure

[ https://issues.apache.org/jira/browse/FLINK-20618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 updated FLINK-20618: Attachment: 2020-12-17 16-45-00 的屏幕截图.png > Some of the source operator subtasks will stuck when

[jira] [Commented] (FLINK-20618) Some of the source operator subtasks will stuck when flink job in critical backpressure

[ https://issues.apache.org/jira/browse/FLINK-20618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17250917#comment-17250917 ] zlzhang0122 commented on FLINK-20618: - Sure, [~pnowojski] . 1. This is a sql job and the logic is

[jira] [Comment Edited] (FLINK-20618) Some of the source operator subtasks will stuck when flink job in critical backpressure

[ https://issues.apache.org/jira/browse/FLINK-20618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17250917#comment-17250917 ] zlzhang0122 edited comment on FLINK-20618 at 12/17/20, 9:07 AM: Sure,

[jira] [Created] (FLINK-19876) Latency metrics can merge chain task latency metrics to reduce the number of latency metrics

zlzhang0122 created FLINK-19876: --- Summary: Latency metrics can merge chain task latency metrics to reduce the number of latency metrics Key: FLINK-19876 URL: https://issues.apache.org/jira/browse/FLINK-19876

[jira] [Commented] (FLINK-19876) Latency metrics can merge chain task latency metrics to reduce the number of latency metrics

[ https://issues.apache.org/jira/browse/FLINK-19876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17223439#comment-17223439 ] zlzhang0122 commented on FLINK-19876: - ah, I see. [~mapohl] thanks for your reply. > Latency

[jira] [Closed] (FLINK-19876) Latency metrics can merge chain task latency metrics to reduce the number of latency metrics

[ https://issues.apache.org/jira/browse/FLINK-19876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 closed FLINK-19876. --- Resolution: Won't Fix > Latency metrics can merge chain task latency metrics to reduce the number

[jira] [Commented] (FLINK-20800) HadoopViewFileSystemTruncateTest failure caused by AssumptionViolatedException

[ https://issues.apache.org/jira/browse/FLINK-20800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17256330#comment-17256330 ] zlzhang0122 commented on FLINK-20800: - [~chesnay] Thanks for your reply. You are right, the reason

[jira] [Comment Edited] (FLINK-20815) Elasticsearch7DynamicSinkITCase failed caused by pulling docker image error

[ https://issues.apache.org/jira/browse/FLINK-20815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17256344#comment-17256344 ] zlzhang0122 edited comment on FLINK-20815 at 12/30/20, 7:19 AM: This

[jira] [Comment Edited] (FLINK-20800) HadoopViewFileSystemTruncateTest failure caused by AssumptionViolatedException

[ https://issues.apache.org/jira/browse/FLINK-20800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17255878#comment-17255878 ] zlzhang0122 edited comment on FLINK-20800 at 12/30/20, 3:35 AM: -I think

[jira] [Created] (FLINK-20815) Elasticsearch7DynamicSinkITCase failed caused by pulling docker image error

zlzhang0122 created FLINK-20815: --- Summary: Elasticsearch7DynamicSinkITCase failed caused by pulling docker image error Key: FLINK-20815 URL: https://issues.apache.org/jira/browse/FLINK-20815 Project:

[jira] [Commented] (FLINK-20815) Elasticsearch7DynamicSinkITCase failed caused by pulling docker image error

[ https://issues.apache.org/jira/browse/FLINK-20815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17256344#comment-17256344 ] zlzhang0122 commented on FLINK-20815: - This problem maybe relate to

[jira] [Commented] (FLINK-20735) Support configurable log level

[ https://issues.apache.org/jira/browse/FLINK-20735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17258744#comment-17258744 ] zlzhang0122 commented on FLINK-20735: - [~trohrmann] Thanks for your reply. Indeed One could replace

[jira] [Commented] (FLINK-20735) Support configurable log level

[ https://issues.apache.org/jira/browse/FLINK-20735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17258834#comment-17258834 ] zlzhang0122 commented on FLINK-20735: - [~trohrmann] Yep, this's exactly what I mean. > Support

[jira] [Updated] (FLINK-20891) SystemResourcesCounterTest may caused endless loop when some error occured

[ https://issues.apache.org/jira/browse/FLINK-20891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 updated FLINK-20891: Description: When the function run() in  class SystemResourcesCounter  come across Throwable

[jira] [Commented] (FLINK-20735) Support configurable log level

[ https://issues.apache.org/jira/browse/FLINK-20735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17260923#comment-17260923 ] zlzhang0122 commented on FLINK-20735: - I agree with you [~trohrmann] , on yarn session-cluster mode,

[jira] [Closed] (FLINK-20800) HadoopViewFileSystemTruncateTest failure caused by AssumptionViolatedException

[ https://issues.apache.org/jira/browse/FLINK-20800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 closed FLINK-20800. --- Resolution: Not A Problem > HadoopViewFileSystemTruncateTest failure caused by

[jira] [Created] (FLINK-21120) Add support for ignore abnormal watermark

zlzhang0122 created FLINK-21120: --- Summary: Add support for ignore abnormal watermark Key: FLINK-21120 URL: https://issues.apache.org/jira/browse/FLINK-21120 Project: Flink Issue Type:

[jira] [Updated] (FLINK-21120) Add support for ignore abnormal watermark

[ https://issues.apache.org/jira/browse/FLINK-21120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 updated FLINK-21120: Description: When using eventTime and extract watermark from element timestamp to generate

[jira] [Updated] (FLINK-20618) Some of the source operator subtasks will stuck when flink job in critical backpressure

[ https://issues.apache.org/jira/browse/FLINK-20618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 updated FLINK-20618: Attachment: 2020-12-16 11-48-30 的屏幕截图.png 2020-12-16 11-47-37 的屏幕截图.png > Some of

[jira] [Updated] (FLINK-20618) Some of the source operator subtasks will stuck when flink job in critical backpressure

[ https://issues.apache.org/jira/browse/FLINK-20618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 updated FLINK-20618: Attachment: 2020-12-16 11-53-42 的屏幕截图.png 2020-12-16 11-49-01 的屏幕截图.png > Some of

[jira] [Commented] (FLINK-20618) Some of the source operator subtasks will stuck when flink job in critical backpressure

[ https://issues.apache.org/jira/browse/FLINK-20618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17250145#comment-17250145 ] zlzhang0122 commented on FLINK-20618: - We found this maybe related to the sequence number is not

[jira] [Comment Edited] (FLINK-20618) Some of the source operator subtasks will stuck when flink job in critical backpressure

[ https://issues.apache.org/jira/browse/FLINK-20618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17250145#comment-17250145 ] zlzhang0122 edited comment on FLINK-20618 at 12/16/20, 7:19 AM: We found

[jira] [Created] (FLINK-20618) Some of the source operator subtasks will stuck when flink job in critical backpressure

zlzhang0122 created FLINK-20618: --- Summary: Some of the source operator subtasks will stuck when flink job in critical backpressure Key: FLINK-20618 URL: https://issues.apache.org/jira/browse/FLINK-20618

[jira] [Comment Edited] (FLINK-20618) Some of the source operator subtasks will stuck when flink job in critical backpressure

[ https://issues.apache.org/jira/browse/FLINK-20618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17250145#comment-17250145 ] zlzhang0122 edited comment on FLINK-20618 at 12/16/20, 7:18 AM: We found

[jira] [Comment Edited] (FLINK-20618) Some of the source operator subtasks will stuck when flink job in critical backpressure

[ https://issues.apache.org/jira/browse/FLINK-20618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17250145#comment-17250145 ] zlzhang0122 edited comment on FLINK-20618 at 12/16/20, 7:20 AM: We found

[jira] [Updated] (FLINK-21165) Timestamps/Watermarks chained erroneously with previous operator

[ https://issues.apache.org/jira/browse/FLINK-21165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 updated FLINK-21165: Description: When using assignTimestampAndWatermarks function separately, if it can satisfied

[jira] [Created] (FLINK-21165) Timestamps/Watermarks chained erroneously with previous operator

zlzhang0122 created FLINK-21165: --- Summary: Timestamps/Watermarks chained erroneously with previous operator Key: FLINK-21165 URL: https://issues.apache.org/jira/browse/FLINK-21165 Project: Flink

[jira] [Commented] (FLINK-22447) when job failed and restore from rocksdb, it produced a exception "Could not load the native RocksDB library"

[ https://issues.apache.org/jira/browse/FLINK-22447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17347616#comment-17347616 ] zlzhang0122 commented on FLINK-22447: - [~yunta] OK, If I have any progress on this, I will comment

[jira] [Commented] (FLINK-22711) NoClassDefFoundError when running Flink 1.11.1 in openJDK8u292-b10

[ https://issues.apache.org/jira/browse/FLINK-22711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17347644#comment-17347644 ] zlzhang0122 commented on FLINK-22711: - [~mapohl]  Thanks for your reply and I agree with you, it's

[jira] [Updated] (FLINK-22711) NoClassDefFoundError when running Flink 1.11.1 in openJDK8u292-b10

[ https://issues.apache.org/jira/browse/FLINK-22711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 updated FLINK-22711: Description: I'm running Flink 1.11.1 on yarn and when I use openJDK8u292-b10(which is the

[jira] [Created] (FLINK-22711) NoClassDefFoundError when running Flink 1.11.1 in openJDK8u292-b10

zlzhang0122 created FLINK-22711: --- Summary: NoClassDefFoundError when running Flink 1.11.1 in openJDK8u292-b10 Key: FLINK-22711 URL: https://issues.apache.org/jira/browse/FLINK-22711 Project: Flink

[jira] [Commented] (FLINK-22447) when job failed and restore from rocksdb, it produced a exception "Could not load the native RocksDB library"

[ https://issues.apache.org/jira/browse/FLINK-22447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17347421#comment-17347421 ] zlzhang0122 commented on FLINK-22447: - [~yunta] No, this problem can hardly reproduce and I didn't

[jira] [Updated] (FLINK-22711) NoClassDefFoundError when running Flink 1.11.1 in openJDK8u292-b10

[ https://issues.apache.org/jira/browse/FLINK-22711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 updated FLINK-22711: Description: I'm running Flink 1.11.1 on yarn and when I use openJDK8u292-b10(which is the

[jira] [Commented] (FLINK-23189) Count and fail the task when the disk is error on JobManager

[ https://issues.apache.org/jira/browse/FLINK-23189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17377391#comment-17377391 ] zlzhang0122 commented on FLINK-23189: - Hi [~pnowojski] I'd like to give this a try, I have done some

[jira] [Created] (FLINK-23189) Count and fail the task when the disk is error on JobManager

zlzhang0122 created FLINK-23189: --- Summary: Count and fail the task when the disk is error on JobManager Key: FLINK-23189 URL: https://issues.apache.org/jira/browse/FLINK-23189 Project: Flink

[jira] [Updated] (FLINK-23189) Count and fail the task when the disk is error on JobManager

[ https://issues.apache.org/jira/browse/FLINK-23189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 updated FLINK-23189: Component/s: Runtime / Checkpointing > Count and fail the task when the disk is error on

[jira] [Updated] (FLINK-23194) Cache and reuse the ContainerLaunchContext and accelarate the progress of createTaskExecutorLaunchContext on yarn

[ https://issues.apache.org/jira/browse/FLINK-23194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 updated FLINK-23194: Description: When starting the TaskExecutor in container on yarn, this will create 

[jira] [Created] (FLINK-23194) Cache and reuse the ContainerLaunchContext and accelarate the progress of createTaskExecutorLaunchContext on yarn

zlzhang0122 created FLINK-23194: --- Summary: Cache and reuse the ContainerLaunchContext and accelarate the progress of createTaskExecutorLaunchContext on yarn Key: FLINK-23194 URL:

[jira] [Commented] (FLINK-22711) NoClassDefFoundError when running Flink 1.11.1 in openJDK8u292-b10

[ https://issues.apache.org/jira/browse/FLINK-22711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17372058#comment-17372058 ] zlzhang0122 commented on FLINK-22711: - [~chesnay] Yeah, this bug can only be reproduced in the

[jira] [Updated] (FLINK-23194) Cache and reuse the ContainerLaunchContext and accelarate the progress of createTaskExecutorLaunchContext on yarn

[ https://issues.apache.org/jira/browse/FLINK-23194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 updated FLINK-23194: Description: When starting the TaskExecutor in container on yarn, this will create 

[jira] [Updated] (FLINK-23189) Count and fail the task when the disk is error on JobManager

[ https://issues.apache.org/jira/browse/FLINK-23189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 updated FLINK-23189: Attachment: exception.txt > Count and fail the task when the disk is error on JobManager >

[jira] [Commented] (FLINK-23194) Cache and reuse the ContainerLaunchContext and accelarate the progress of createTaskExecutorLaunchContext on yarn

[ https://issues.apache.org/jira/browse/FLINK-23194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17376184#comment-17376184 ] zlzhang0122 commented on FLINK-23194: - [~trohrmann] [~pnowojski] 

[jira] [Comment Edited] (FLINK-23194) Cache and reuse the ContainerLaunchContext and accelarate the progress of createTaskExecutorLaunchContext on yarn

[ https://issues.apache.org/jira/browse/FLINK-23194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17376184#comment-17376184 ] zlzhang0122 edited comment on FLINK-23194 at 7/7/21, 3:15 AM: -- [~trohrmann]

[jira] [Commented] (FLINK-23189) Count and fail the task when the disk is error on JobManager

[ https://issues.apache.org/jira/browse/FLINK-23189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17376181#comment-17376181 ] zlzhang0122 commented on FLINK-23189: - sure, [~pnowojski] I have posted a attachment which record

[jira] [Created] (FLINK-22447) when job failed and restore from rocksdb, it produced a exception "Could not load the native RocksDB library"

zlzhang0122 created FLINK-22447: --- Summary: when job failed and restore from rocksdb, it produced a exception "Could not load the native RocksDB library" Key: FLINK-22447 URL:

[jira] [Created] (FLINK-22091) env.java.home option didn't take effect in resource negotiator

zlzhang0122 created FLINK-22091: --- Summary: env.java.home option didn't take effect in resource negotiator Key: FLINK-22091 URL: https://issues.apache.org/jira/browse/FLINK-22091 Project: Flink

[jira] [Closed] (FLINK-20735) Support different log levels per job

[ https://issues.apache.org/jira/browse/FLINK-20735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 closed FLINK-20735. --- Resolution: Won't Fix > Support different log levels per job >

[jira] [Closed] (FLINK-20367) Show the in-use config of job to users

[ https://issues.apache.org/jira/browse/FLINK-20367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 closed FLINK-20367. --- Resolution: Won't Fix > Show the in-use config of job to users >

[jira] [Commented] (FLINK-20367) Show the in-use config of job to users

[ https://issues.apache.org/jira/browse/FLINK-20367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313097#comment-17313097 ] zlzhang0122 commented on FLINK-20367: - sorry for the late reply, I have solved it by another way and

[jira] [Closed] (FLINK-23622) Default filesystem scheme improvement

[ https://issues.apache.org/jira/browse/FLINK-23622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zlzhang0122 closed FLINK-23622. --- Resolution: Not A Problem > Default filesystem scheme improvement >

[jira] [Created] (FLINK-23849) Support react to the node decommissioning change state on yarn and do graceful restart

zlzhang0122 created FLINK-23849: --- Summary: Support react to the node decommissioning change state on yarn and do graceful restart Key: FLINK-23849 URL: https://issues.apache.org/jira/browse/FLINK-23849

  1   2   3   >