[jira] [Commented] (FLINK-14815) Expose network metric for sub task in rest api

2020-09-14 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-14815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17195291#comment-17195291 ] lining commented on FLINK-14815: It is still valid. > Expose network metric for sub tas

[jira] [Commented] (FLINK-14435) Add TaskManageResourceInfo which match the memory compositions of taskmanager

2020-09-14 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-14435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17195285#comment-17195285 ] lining commented on FLINK-14435: The previous configuration doesn't fully reflect the me

[jira] [Commented] (FLINK-17328) Expose network metric for job vertex in rest api

2020-09-14 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-17328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17195262#comment-17195262 ] lining commented on FLINK-17328: WebUI has monitor backpressure. But users need to know

[jira] [Commented] (FLINK-15170) WebFrontendITCase.testCancelYarn fails on travis

2020-08-10 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-15170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174264#comment-17174264 ] lining commented on FLINK-15170: According to the current message, it can be determined

[jira] [Updated] (FLINK-18347) kinesis connector throw Error java.lang.NoSuchFieldError: NO_INTS

2020-06-17 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-18347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-18347: --- Summary: kinesis connector throw Error java.lang.NoSuchFieldError: NO_INTS (was: Error java.lang.NoSuchFiel

[jira] [Created] (FLINK-18347) Error java.lang.NoSuchFieldError: NO_INTS

2020-06-17 Thread lining (Jira)
lining created FLINK-18347: -- Summary: Error java.lang.NoSuchFieldError: NO_INTS Key: FLINK-18347 URL: https://issues.apache.org/jira/browse/FLINK-18347 Project: Flink Issue Type: Bug Compo

[jira] [Commented] (FLINK-17378) KafkaProducerExactlyOnceITCase>KafkaProducerTestBase.testExactlyOnceCustomOperator unstable

2020-05-18 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-17378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17110852#comment-17110852 ] lining commented on FLINK-17378: Another instance:  [https://dev.azure.com/apache-flink/

[jira] [Updated] (FLINK-17328) Expose network metric for job vertex in rest api

2020-04-25 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-17328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-17328: --- Description: JobDetailsHandler * pool usage: outPoolUsageAvg, inputExclusiveBuffersUsageAvg,  inputFloating

[jira] [Comment Edited] (FLINK-17328) Expose network metric for job vertex in rest api

2020-04-22 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-17328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17090203#comment-17090203 ] lining edited comment on FLINK-17328 at 4/23/20, 3:40 AM: -- [Gar

[jira] [Commented] (FLINK-17328) Expose network metric for job vertex in rest api

2020-04-22 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-17328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17090203#comment-17090203 ] lining commented on FLINK-17328: [~gary] could you assign it to me? > Expose network me

[jira] [Updated] (FLINK-14815) Expose network metric for sub task in rest api

2020-04-22 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-14815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-14815: --- Description: * SubTask **  pool usage: outPoolUsage, inputExclusiveBuffersUsage,  inputFloatingBuffersUsage

[jira] [Updated] (FLINK-17328) Expose network metric for job vertex in rest api

2020-04-22 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-17328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-17328: --- Description: JobVertexDetailsHandler * pool usage: outPoolUsageAvg, inputExclusiveBuffersUsageAvg,  inputFl

[jira] [Updated] (FLINK-14815) Expose network metric for sub task in rest api

2020-04-22 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-14815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-14815: --- Summary: Expose network metric for sub task in rest api (was: Expose network metric in rest api) > Expose

[jira] [Updated] (FLINK-17328) Expose network metric for job vertex in rest api

2020-04-22 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-17328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-17328: --- Parent: FLINK-14712 Issue Type: Sub-task (was: Improvement) > Expose network metric for job vertex

[jira] [Created] (FLINK-17328) Expose network metric for job vertex in rest api

2020-04-22 Thread lining (Jira)
lining created FLINK-17328: -- Summary: Expose network metric for job vertex in rest api Key: FLINK-17328 URL: https://issues.apache.org/jira/browse/FLINK-17328 Project: Flink Issue Type: Improvement

[jira] [Updated] (FLINK-13510) Show fail attempt for subtask in timelime In Rest API

2020-04-15 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-13510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-13510: --- Description: Now, a user just can see subtask current attempt in the timeline. If job failover, can not see

[jira] [Updated] (FLINK-14713) Show All Attempts For Vertex SubTask In Rest Api

2020-04-15 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-14713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-14713: --- Description: Flink jobs could recovery by failover, but the user couldn't see any information about the job

[jira] [Comment Edited] (FLINK-14713) Show All Attempts For Vertex SubTask In Rest Api

2020-04-14 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-14713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17083126#comment-17083126 ] lining edited comment on FLINK-14713 at 4/14/20, 11:35 AM: --- Hi

[jira] [Commented] (FLINK-14713) Show All Attempts For Vertex SubTask In Rest Api

2020-04-14 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-14713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17083126#comment-17083126 ] lining commented on FLINK-14713: [~gjy] > Show All Attempts For Vertex SubTask In Rest

[jira] [Updated] (FLINK-13510) Show fail attempt for subtask in timelime In Rest API

2020-04-13 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-13510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-13510: --- Description: Now, a user just can see subtask current attempt in the timeline. If job failover, can not see

[jira] [Updated] (FLINK-13510) Show fail attempt for subtask in timelime In Rest API

2020-04-13 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-13510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-13510: --- Description: Now, a user just can see subtask current attempt in the timeline. If job failover, can not see

[jira] [Updated] (FLINK-13510) Show fail attempt for subtask in timelime In Rest API

2020-04-13 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-13510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-13510: --- Description: Now, user just can see subtask current attempt in timeline. If job failover, can not see some

[jira] [Updated] (FLINK-14713) Show All Attempts For Vertex SubTask In Rest Api

2020-04-13 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-14713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-14713: --- Description: Flink jobs could recovery by failover, but the user couldn't see any information about the job

[jira] [Updated] (FLINK-14137) Show Attempt List in Vertex SubTask In WebUI

2020-04-08 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-14137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-14137: --- Summary: Show Attempt List in Vertex SubTask In WebUI (was: Show Attempt History in Vertex SubTask In WebUI

[jira] [Updated] (FLINK-14713) Show All Attempts For Vertex SubTask In Rest Api

2020-04-08 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-14713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-14713: --- Summary: Show All Attempts For Vertex SubTask In Rest Api (was: Show Historical Attempt For Vertex SubTask

[jira] [Updated] (FLINK-14713) Show Historical Attempt For Vertex SubTask In Rest Api

2020-04-03 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-14713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-14713: --- Description: Flink jobs could recovery by failover, but the user couldn't see any information about the job

[jira] [Updated] (FLINK-14713) Show Historical Attempt For Vertex SubTask In Rest Api

2020-04-03 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-14713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-14713: --- Description: Flink jobs could recovery by failover, but the user couldn't see any information about the job

[jira] [Updated] (FLINK-14713) Show Historical Attempt For Vertex SubTask In Rest Api

2020-04-03 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-14713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-14713: --- Summary: Show Historical Attempt For Vertex SubTask In Rest Api (was: Show Attempt History in Vertex SubTas

[jira] [Updated] (FLINK-14713) Show Attempt History in Vertex SubTask In Rest Api

2020-04-03 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-14713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-14713: --- Description: Flink jobs could recovery by failover, but the user couldn't see any information about the job

[jira] [Updated] (FLINK-14713) Show Attempt History in Vertex SubTask In Rest Api

2020-04-02 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-14713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-14713: --- Description: Flink jobs could recovery by failover, but the user couldn't see any information about the job

[jira] [Updated] (FLINK-14713) Show Attempt History in Vertex SubTask In Rest Api

2020-04-02 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-14713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-14713: --- Description: Flink jobs could recovery by failover, but the user couldn't see any information about the job

[jira] [Updated] (FLINK-14143) Failed Attempts display in the timeline

2020-04-01 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-14143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-14143: --- Summary: Failed Attempts display in the timeline (was: Failed Attempt does display in the timeline) > Fail

[jira] [Updated] (FLINK-14143) Failed Attempt does display in the timeline

2020-04-01 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-14143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-14143: --- Summary: Failed Attempt does display in the timeline (was: Failed Attempt does not display in the timeline)

[jira] [Updated] (FLINK-16863) Sorting descendingly on the last modified date of LogInfo

2020-03-30 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-16863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-16863: --- Summary: Sorting descendingly on the last modified date of LogInfo (was: add lastModified as a field of Log

[jira] [Updated] (FLINK-16863) add lastModified as a field of LogInfo

2020-03-30 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-16863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-16863: --- Parent: FLINK-13987 Issue Type: Sub-task (was: Improvement) > add lastModified as a field of LogInf

[jira] [Created] (FLINK-16863) add lastModified as a field of LogInfo

2020-03-30 Thread lining (Jira)
lining created FLINK-16863: -- Summary: add lastModified as a field of LogInfo Key: FLINK-16863 URL: https://issues.apache.org/jira/browse/FLINK-16863 Project: Flink Issue Type: Improvement

[jira] [Updated] (FLINK-13987) add log list and read log by name

2020-03-04 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-13987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-13987: --- Description: As the job running, the log files are becoming large. As the application runs on JVM, sometime

[jira] [Updated] (FLINK-16302) add log list and read log by name for taskmanager

2020-03-04 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-16302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-16302: --- Description: *  list taskmanager all log file ** /taskmanagers/taskmanagerid/logs ** {code:java} { "log

[jira] [Commented] (FLINK-11546) Add option to manually set job ID in CLI

2020-03-01 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-11546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17048772#comment-17048772 ] lining commented on FLINK-11546: ping [~trohrmann]  > Add option to manually set job ID

[jira] [Comment Edited] (FLINK-13987) add log list and read log by name

2020-03-01 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-13987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17048771#comment-17048771 ] lining edited comment on FLINK-13987 at 3/2/20 4:05 AM: ping [~g

[jira] [Commented] (FLINK-13987) add log list and read log by name

2020-03-01 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-13987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17048771#comment-17048771 ] lining commented on FLINK-13987: ping [~gary]. > add log list and read log by name > --

[jira] [Commented] (FLINK-15314) To refactor duplicated code in TaskManagerDetailsHandler#createTaskManagerMetricsInfo

2020-03-01 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-15314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17048768#comment-17048768 ] lining commented on FLINK-15314: Hi [~gjy] , I encountered a specific problem: If some d

[jira] [Commented] (FLINK-15314) To refactor duplicated code in TaskManagerDetailsHandler#createTaskManagerMetricsInfo

2020-02-28 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-15314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17047619#comment-17047619 ] lining commented on FLINK-15314: Thanks for your reply, I have updated the code link. >

[jira] [Updated] (FLINK-15314) To refactor duplicated code in TaskManagerDetailsHandler#createTaskManagerMetricsInfo

2020-02-28 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-15314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-15314: --- Description: As  [code|https://github.com/apache/flink/blob/master/flink-runtime/src/main/java/org/apache/fl

[jira] [Updated] (FLINK-15314) To refactor duplicated code in TaskManagerDetailsHandler#createTaskManagerMetricsInfo

2020-02-28 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-15314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-15314: --- Description: As  [code|[https://github.com/apache/flink/blob/master/flink-runtime/src/main/java/org/apache/f

[jira] [Updated] (FLINK-13987) add log list and read log by name

2020-02-27 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-13987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-13987: --- Summary: add log list and read log by name (was: add new logs api, see more log files) > add log list and

[jira] [Updated] (FLINK-16303) add log list and read log by name for jobmanager

2020-02-27 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-16303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-16303: --- Description: * list jobmanager all log file ** /jobmanager/logs ** {code:java} { "logs": [ {

[jira] [Updated] (FLINK-16302) add log list and read log by name for taskmanager

2020-02-27 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-16302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-16302: --- Description: *  list taskmanager all log file ** /taskmanagers/taskmanagerid/logs ** {code:java} { "log

[jira] [Created] (FLINK-16303) add log list and read log by name for jobmanager

2020-02-27 Thread lining (Jira)
lining created FLINK-16303: -- Summary: add log list and read log by name for jobmanager Key: FLINK-16303 URL: https://issues.apache.org/jira/browse/FLINK-16303 Project: Flink Issue Type: Sub-task

[jira] [Created] (FLINK-16302) add log list and read log by name for taskmanager

2020-02-27 Thread lining (Jira)
lining created FLINK-16302: -- Summary: add log list and read log by name for taskmanager Key: FLINK-16302 URL: https://issues.apache.org/jira/browse/FLINK-16302 Project: Flink Issue Type: Sub-task

[jira] [Updated] (FLINK-13987) add new logs api, see more log files

2020-02-27 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-13987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-13987: --- Summary: add new logs api, see more log files (was: add new logs api, see more log files and can see logs b

[jira] [Updated] (FLINK-13987) add new logs api, see more log files and can see logs by pages

2020-02-26 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-13987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-13987: --- Description: As the job running, the log files are becoming large. As the application runs on JVM, sometime

[jira] [Updated] (FLINK-13987) add new logs api, see more log files and can see logs by pages

2020-02-26 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-13987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-13987: --- Description: As the job running, the log files are becoming large. As the application runs on JVM, sometime

[jira] [Updated] (FLINK-13987) add new logs api, see more log files and can see logs by pages

2020-02-25 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-13987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-13987: --- Description: As the job running, the log files are becoming large. Current log API returns all contents,it

[jira] [Updated] (FLINK-13987) add new logs api, see more log files and can see logs by pages

2020-02-25 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-13987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-13987: --- Description: As the job running, the log files are becoming large. As the application runs on JVM, sometime

[jira] [Updated] (FLINK-13987) add new logs api, see more log files and can see logs by pages

2020-02-25 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-13987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-13987: --- Description: As the job running, the log files are becoming large. As the application runs on JVM, sometime

[jira] [Commented] (FLINK-13987) add new logs api, see more log files and can see logs by pages

2020-02-25 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-13987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17044241#comment-17044241 ] lining commented on FLINK-13987: As FLIP-103 has approved, could someone assign it to me

[jira] [Commented] (FLINK-11546) Add option to manually set job ID in CLI

2020-02-24 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-11546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17044160#comment-17044160 ] lining commented on FLINK-11546: [~uce] could you assign it to me? > Add option to manu

[jira] [Closed] (FLINK-16184) Submit job with fixed/configurable JobID

2020-02-20 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-16184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining closed FLINK-16184. -- Resolution: Duplicate > Submit job with fixed/configurable JobID > -

[jira] [Commented] (FLINK-11546) Add option to manually set job ID in CLI

2020-02-20 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-11546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17040779#comment-17040779 ] lining commented on FLINK-11546: [~yanghua], how is this going now? > Add option to man

[jira] [Updated] (FLINK-16184) Submit job with fixed/configurable JobID

2020-02-20 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-16184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-16184: --- Description: Now the user could define jobId when the user submit job by  JarRunHandler. But we couldn't defi

[jira] [Created] (FLINK-16184) Submit job with fixed/configurable JobID

2020-02-20 Thread lining (Jira)
lining created FLINK-16184: -- Summary: Submit job with fixed/configurable JobID Key: FLINK-16184 URL: https://issues.apache.org/jira/browse/FLINK-16184 Project: Flink Issue Type: Improvement

[jira] [Updated] (FLINK-14138) Show Pending Slots in Job Detail

2020-02-13 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-14138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-14138: --- Component/s: Runtime / REST > Show Pending Slots in Job Detail > > >

[jira] [Updated] (FLINK-14730) Add pending slots for job

2020-02-13 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-14730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-14730: --- Parent: FLINK-14138 Issue Type: Sub-task (was: Improvement) > Add pending slots for job > -

[jira] [Updated] (FLINK-14730) Add pending slots for job

2020-02-13 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-14730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-14730: --- Component/s: (was: Runtime / Web Frontend) > Add pending slots for job > - > >

[jira] [Updated] (FLINK-13510) Show fail attempt for subtask in timelime

2020-02-13 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-13510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-13510: --- Component/s: (was: Runtime / Web Frontend) > Show fail attempt for subtask in timelime > ---

[jira] [Updated] (FLINK-13510) Show fail attempt for subtask in timelime In Rest API

2020-02-13 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-13510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-13510: --- Summary: Show fail attempt for subtask in timelime In Rest API (was: Show fail attempt for subtask in timel

[jira] [Updated] (FLINK-14137) Show Attempt History in Vertex SubTask In WebUI

2020-02-13 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-14137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-14137: --- Summary: Show Attempt History in Vertex SubTask In WebUI (was: Show Attempt History in Vertex SubTask) > S

[jira] [Updated] (FLINK-14713) Show Attempt History in Vertex SubTask In Rest Api

2020-02-13 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-14713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-14713: --- Component/s: (was: Runtime / Web Frontend) > Show Attempt History in Vertex SubTask In Rest Api > --

[jira] [Updated] (FLINK-14713) Show Attempt History in Vertex SubTask In Rest Api

2020-02-13 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-14713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-14713: --- Summary: Show Attempt History in Vertex SubTask In Rest Api (was: Show Attempt History in Vertex SubTask)

[jira] [Updated] (FLINK-13510) Show fail attempt for subtask in timelime

2020-02-13 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-13510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-13510: --- Parent: FLINK-16050 Issue Type: Sub-task (was: Improvement) > Show fail attempt for subtask in time

[jira] [Updated] (FLINK-14143) Failed Attempt does not display in the timeline

2020-02-13 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-14143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-14143: --- Parent: FLINK-16050 Issue Type: Sub-task (was: Improvement) > Failed Attempt does not display in th

[jira] [Updated] (FLINK-14713) Show Attempt History in Vertex SubTask

2020-02-13 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-14713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-14713: --- Parent: FLINK-16050 Issue Type: Sub-task (was: Improvement) > Show Attempt History in Vertex SubTas

[jira] [Updated] (FLINK-14137) Show Attempt History in Vertex SubTask

2020-02-13 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-14137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-14137: --- Parent: (was: FLINK-14713) Issue Type: Task (was: Sub-task) > Show Attempt History in Vertex Su

[jira] [Updated] (FLINK-14137) Show Attempt History in Vertex SubTask

2020-02-13 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-14137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-14137: --- Parent: FLINK-16050 Issue Type: Sub-task (was: Task) > Show Attempt History in Vertex SubTask > ---

[jira] [Created] (FLINK-16050) Add Attempt Information

2020-02-13 Thread lining (Jira)
lining created FLINK-16050: -- Summary: Add Attempt Information Key: FLINK-16050 URL: https://issues.apache.org/jira/browse/FLINK-16050 Project: Flink Issue Type: Improvement Components: Run

[jira] [Updated] (FLINK-14127) Better BackPressure Detection in WebUI

2020-02-13 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-14127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-14127: --- Parent: FLINK-14712 Issue Type: Sub-task (was: Improvement) > Better BackPressure Detection in WebU

[jira] [Commented] (FLINK-15422) Expose Jvm Metaspace、Compressed Class Space、Eden Space、Survivor Space、Old Gen metric

2020-02-03 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-15422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17028790#comment-17028790 ] lining commented on FLINK-15422: We could get these information from _ManagementFactory.

[jira] [Commented] (FLINK-15752) Backpressure stats sometimes broken in WebUI

2020-02-03 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-15752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17028771#comment-17028771 ] lining commented on FLINK-15752: [~NicoK], could you show the result from rest API? > B

[jira] [Issue Comment Deleted] (FLINK-15752) Backpressure stats sometimes broken in WebUI

2020-02-03 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-15752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-15752: --- Comment: was deleted (was: [~NicoK] could you show the result from the rest API?) > Backpressure stats some

[jira] [Commented] (FLINK-15752) Backpressure stats sometimes broken in WebUI

2020-02-03 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-15752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17028760#comment-17028760 ] lining commented on FLINK-15752: [~NicoK] could you show the result from the rest API?

[jira] [Commented] (FLINK-15628) Fix initialize webSubmissionHandlers list in WebSubmissionExtension with correct size

2020-01-19 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-15628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17019192#comment-17019192 ] lining commented on FLINK-15628: Hi, [~GJL] could you assign it to me? > Fix initialize

[jira] [Updated] (FLINK-15423) Show the detail of submitting job fail

2020-01-19 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-15423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-15423: --- Description: Now when the user fails to submit the job, could we return the details of the failure? For ex

[jira] [Updated] (FLINK-15315) Add test case for rest

2020-01-19 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-15315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-15315: --- Description: 1. Handler which has no test: * ClusterConfigHandler * ClusterOverviewHandler * DashboardCon

[jira] [Commented] (FLINK-15628) Fix initialize webSubmissionHandlers list in WebSubmissionExtension with correct size

2020-01-17 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-15628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17017823#comment-17017823 ] lining commented on FLINK-15628: cc [~gjy]  > Fix initialize webSubmissionHandlers list

[jira] [Created] (FLINK-15628) Fix initialize webSubmissionHandlers list in WebSubmissionExtension with correct size

2020-01-17 Thread lining (Jira)
lining created FLINK-15628: -- Summary: Fix initialize webSubmissionHandlers list in WebSubmissionExtension with correct size Key: FLINK-15628 URL: https://issues.apache.org/jira/browse/FLINK-15628 Project: Fl

[jira] [Issue Comment Deleted] (FLINK-15489) Cannot update jobmanager/taskmanager logs

2020-01-09 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-15489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-15489: --- Comment: was deleted (was: As [~vthinkxie] said, it's to reduce the pressure of the rest server. As the API

[jira] [Commented] (FLINK-15489) Cannot update jobmanager/taskmanager logs

2020-01-09 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-15489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17011667#comment-17011667 ] lining commented on FLINK-15489: As [~vthinkxie] said, it's to reduce the pressure of th

[jira] [Comment Edited] (FLINK-15170) WebFrontendITCase.testCancelYarn fails on travis

2019-12-30 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-15170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17005207#comment-17005207 ] lining edited comment on FLINK-15170 at 12/30/19 9:17 AM: -- Disc

[jira] [Comment Edited] (FLINK-15170) WebFrontendITCase.testCancelYarn fails on travis

2019-12-30 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-15170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17005207#comment-17005207 ] lining edited comment on FLINK-15170 at 12/30/19 9:13 AM: -- Disc

[jira] [Comment Edited] (FLINK-15170) WebFrontendITCase.testCancelYarn fails on travis

2019-12-30 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-15170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17005207#comment-17005207 ] lining edited comment on FLINK-15170 at 12/30/19 8:53 AM: -- Disc

[jira] [Commented] (FLINK-15170) WebFrontendITCase.testCancelYarn fails on travis

2019-12-30 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-15170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17005207#comment-17005207 ] lining commented on FLINK-15170: Discover testCancelYarn and testCancel all fail. testCa

[jira] [Updated] (FLINK-15423) Show the detail of submitting job fail

2019-12-27 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-15423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-15423: --- Description: Now when the user fails to submit the job, it just returns: unable to load the requested file.

[jira] [Created] (FLINK-15423) Show the detail of submitting job fail

2019-12-27 Thread lining (Jira)
lining created FLINK-15423: -- Summary: Show the detail of submitting job fail Key: FLINK-15423 URL: https://issues.apache.org/jira/browse/FLINK-15423 Project: Flink Issue Type: Improvement

[jira] [Created] (FLINK-15422) Expose Jvm Metaspace、Compressed Class Space、Eden Space、Survivor Space、Old Gen metric

2019-12-27 Thread lining (Jira)
lining created FLINK-15422: -- Summary: Expose Jvm Metaspace、Compressed Class Space、Eden Space、Survivor Space、Old Gen metric Key: FLINK-15422 URL: https://issues.apache.org/jira/browse/FLINK-15422 Project: Fli

[jira] [Updated] (FLINK-15369) MiniCluster use fixed network / managed memory sizes by default

2019-12-25 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-15369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-15369: --- Summary: MiniCluster use fixed network / managed memory sizes by default (was: MiniCluster use fixed networ

[jira] [Commented] (FLINK-15345) CurrentExecution and priorExecutions are inconsistent in the test case

2019-12-20 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-15345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17000780#comment-17000780 ] lining commented on FLINK-15345: Referring to the  [code|https://github.com/apache/flink

[jira] [Created] (FLINK-15345) CurrentExecution and priorExecutions are inconsistent in the test case

2019-12-20 Thread lining (Jira)
lining created FLINK-15345: -- Summary: CurrentExecution and priorExecutions are inconsistent in the test case Key: FLINK-15345 URL: https://issues.apache.org/jira/browse/FLINK-15345 Project: Flink I

[jira] [Commented] (FLINK-15329) Incorrect comment for MemoryManager#availableMemory

2019-12-19 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-15329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1676#comment-1676 ] lining commented on FLINK-15329: cc [~sewen] > Incorrect comment for MemoryManager#avai

[jira] [Updated] (FLINK-15329) Incorrect comment for MemoryManager#availableMemory

2019-12-19 Thread lining (Jira)
[ https://issues.apache.org/jira/browse/FLINK-15329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lining updated FLINK-15329: --- Description: As the [code|https://github.com/apache/flink/blob/master/flink-runtime/src/main/java/org/apache

  1   2   3   4   5   >