[jira] [Updated] (FLINK-23826) Verify optimized scheduler performance for large-scale jobs
[ https://issues.apache.org/jira/browse/FLINK-23826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu updated FLINK-23826: Description: This ticket is used to verify the result of FLINK-21110. It should check if large scale jobs' scheduling are working well and the scheduling performance, with a real job running on cluster. The conclusion should include, for a *1 --- all-to-all-connected -->1* job: 1. time of job initialization on master (job received -> scheduling started) 2. time of task deployment (task deploying started -> all tasks in RUNNING) 3. time of making task failure recovery decision (JM notified about task failure -> tasks to restart decided) was: This ticket is used to verify the result of FLINK-21110. It should check if large scale jobs' scheduling are working well and the scheduling performance, with a real job running on cluster. The conclusion should include, for a *1 --- all-to-all-connected -->1* job: 1. time of job initialization on master (job received -> scheduling started) 2. time of task deployment (task deploying started -> all tasks in INITIALIZATION) 3. time of making task failure recovery decision (JM notified about task failure -> tasks to restart decided) > Verify optimized scheduler performance for large-scale jobs > --- > > Key: FLINK-23826 > URL: https://issues.apache.org/jira/browse/FLINK-23826 > Project: Flink > Issue Type: Sub-task > Components: Runtime / Coordination >Affects Versions: 1.14.0 >Reporter: Zhu Zhu >Assignee: Zhu Zhu >Priority: Major > Fix For: 1.14.0 > > > This ticket is used to verify the result of FLINK-21110. > It should check if large scale jobs' scheduling are working well and the > scheduling performance, with a real job running on cluster. > The conclusion should include, for a *1 --- all-to-all-connected > -->1* job: > 1. time of job initialization on master (job received -> scheduling started) > 2. time of task deployment (task deploying started -> all tasks in RUNNING) > 3. time of making task failure recovery decision (JM notified about task > failure -> tasks to restart decided) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-23826) Verify optimized scheduler performance for large-scale jobs
[ https://issues.apache.org/jira/browse/FLINK-23826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu updated FLINK-23826: Priority: Major (was: Critical) > Verify optimized scheduler performance for large-scale jobs > --- > > Key: FLINK-23826 > URL: https://issues.apache.org/jira/browse/FLINK-23826 > Project: Flink > Issue Type: Sub-task > Components: Runtime / Coordination >Affects Versions: 1.14.0 >Reporter: Zhu Zhu >Assignee: Zhu Zhu >Priority: Major > Fix For: 1.14.0 > > > This ticket is used to verify the result of FLINK-21110. > It should check if large scale jobs' scheduling are working well and the > scheduling performance, with a real job running on cluster. > The conclusion should include, for a *1 --- all-to-all-connected > -->1* job: > 1. time of job initialization on master (job received -> scheduling started) > 2. time of task deployment (task deploying started -> all tasks in > INITIALIZATION) > 3. time of making task failure recovery decision (JM notified about task > failure -> tasks to restart decided) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-23826) Verify optimized scheduler performance for large-scale jobs
[ https://issues.apache.org/jira/browse/FLINK-23826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu updated FLINK-23826: Description: This ticket is used to verify the result of FLINK-21110. It should check if large scale jobs' scheduling are working well and the scheduling performance, with a real job running on cluster. The conclusion should include, for a *1 --- all-to-all-connected -->1* job: 1. time of job initialization on master (job received -> scheduling started) 2. time of task deployment (task deploying started -> all tasks in INITIALIZATION) 3. time of making task failure recovery decision (JM notified about task failure -> tasks to restart decided) was: This ticket is used to verify the result of FLINK-21110. It should check if large scale jobs' scheduling are working well and the scheduling performance, with a real job running on cluster. The conclusion should include, for a *1 --- all-to-all-connected -->1* job: 1. time of job initialization on master (job received -> scheduling started) 2. time of job scheduling and deployment (scheduling started -> all tasks in INITIALIZATION) 3. time of job restarting on task failover (JM notified about task failure -> all tasks in INITIALIZATION again) > Verify optimized scheduler performance for large-scale jobs > --- > > Key: FLINK-23826 > URL: https://issues.apache.org/jira/browse/FLINK-23826 > Project: Flink > Issue Type: Sub-task > Components: Runtime / Coordination >Affects Versions: 1.14.0 >Reporter: Zhu Zhu >Assignee: Zhu Zhu >Priority: Critical > Fix For: 1.14.0 > > > This ticket is used to verify the result of FLINK-21110. > It should check if large scale jobs' scheduling are working well and the > scheduling performance, with a real job running on cluster. > The conclusion should include, for a *1 --- all-to-all-connected > -->1* job: > 1. time of job initialization on master (job received -> scheduling started) > 2. time of task deployment (task deploying started -> all tasks in > INITIALIZATION) > 3. time of making task failure recovery decision (JM notified about task > failure -> tasks to restart decided) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-23826) Verify optimized scheduler performance for large-scale jobs
[ https://issues.apache.org/jira/browse/FLINK-23826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu updated FLINK-23826: Description: This ticket is used to verify the result of FLINK-21110. It should check if large scale jobs' scheduling are working well and the scheduling performance, with a real job running on cluster. The conclusion should include, for a *1 --- all-to-all-connected -->1* job: 1. time of job initialization on master (job received -> scheduling started) 2. time of job scheduling and deployment (scheduling started -> all tasks in INITIALIZATION) 3. time of job restarting on task failover (JM notified about task failure -> all tasks in INITIALIZATION again) was: This ticket is used to verify the result of FLINK-21110. It should check if large scale jobs' scheduling are working well and the scheduling performance, with a real job running on cluster. The conclusion should include, for a *1 --- all-to-all-connected -->1* job: 1. time of job initialization on master (job received -> scheduling started) 2. time of job scheduling and deployment (scheduling started -> all tasks in INITIALIZATION) 3. time of job restarting on task failover (JM notified about task failure -> all tasks in INITIALIZATION again) 4. master heap memory required > Verify optimized scheduler performance for large-scale jobs > --- > > Key: FLINK-23826 > URL: https://issues.apache.org/jira/browse/FLINK-23826 > Project: Flink > Issue Type: Sub-task > Components: Runtime / Coordination >Affects Versions: 1.14.0 >Reporter: Zhu Zhu >Assignee: Zhu Zhu >Priority: Critical > Fix For: 1.14.0 > > > This ticket is used to verify the result of FLINK-21110. > It should check if large scale jobs' scheduling are working well and the > scheduling performance, with a real job running on cluster. > The conclusion should include, for a *1 --- all-to-all-connected > -->1* job: > 1. time of job initialization on master (job received -> scheduling started) > 2. time of job scheduling and deployment (scheduling started -> all tasks in > INITIALIZATION) > 3. time of job restarting on task failover (JM notified about task failure -> > all tasks in INITIALIZATION again) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-23826) Verify optimized scheduler performance for large-scale jobs
[ https://issues.apache.org/jira/browse/FLINK-23826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu updated FLINK-23826: Priority: Critical (was: Blocker) > Verify optimized scheduler performance for large-scale jobs > --- > > Key: FLINK-23826 > URL: https://issues.apache.org/jira/browse/FLINK-23826 > Project: Flink > Issue Type: Sub-task > Components: Runtime / Coordination >Affects Versions: 1.14.0 >Reporter: Zhu Zhu >Assignee: Zhilong Hong >Priority: Critical > Fix For: 1.14.0 > > > This ticket is used to verify the result of FLINK-21110. > It should check if large scale jobs' scheduling are working well and the > scheduling performance, with a real job running on cluster. > The conclusion should include, for a *1 --- all-to-all-connected > -->1* job: > 1. time of job initialization on master (job received -> scheduling started) > 2. time of job scheduling and deployment (scheduling started -> all tasks in > INITIALIZATION) > 3. time of job restarting on task failover (JM notified about task failure -> > all tasks in INITIALIZATION again) > 4. master heap memory required -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-23826) Verify optimized scheduler performance for large-scale jobs
[ https://issues.apache.org/jira/browse/FLINK-23826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xintong Song updated FLINK-23826: - Labels: (was: release-testing) > Verify optimized scheduler performance for large-scale jobs > --- > > Key: FLINK-23826 > URL: https://issues.apache.org/jira/browse/FLINK-23826 > Project: Flink > Issue Type: Sub-task > Components: Runtime / Coordination >Affects Versions: 1.14.0 >Reporter: Zhu Zhu >Priority: Blocker > Fix For: 1.14.0 > > > This ticket is used to verify the result of FLINK-21110. > It should check if large scale jobs' scheduling are working well and the > scheduling performance, with a real job running on cluster. > The conclusion should include, for a *1 --- all-to-all-connected > -->1* job: > 1. time of job initialization on master (job received -> scheduling started) > 2. time of job scheduling and deployment (scheduling started -> all tasks in > INITIALIZATION) > 3. time of job restarting on task failover (JM notified about task failure -> > all tasks in INITIALIZATION again) > 4. master heap memory required -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-23826) Verify optimized scheduler performance for large-scale jobs
[ https://issues.apache.org/jira/browse/FLINK-23826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xintong Song updated FLINK-23826: - Labels: release-testing (was: ) > Verify optimized scheduler performance for large-scale jobs > --- > > Key: FLINK-23826 > URL: https://issues.apache.org/jira/browse/FLINK-23826 > Project: Flink > Issue Type: Sub-task > Components: Runtime / Coordination >Affects Versions: 1.14.0 >Reporter: Zhu Zhu >Priority: Blocker > Labels: release-testing > Fix For: 1.14.0 > > > This ticket is used to verify the result of FLINK-21110. > It should check if large scale jobs' scheduling are working well and the > scheduling performance, with a real job running on cluster. > The conclusion should include, for a *1 --- all-to-all-connected > -->1* job: > 1. time of job initialization on master (job received -> scheduling started) > 2. time of job scheduling and deployment (scheduling started -> all tasks in > INITIALIZATION) > 3. time of job restarting on task failover (JM notified about task failure -> > all tasks in INITIALIZATION again) > 4. master heap memory required -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-23826) Verify optimized scheduler performance for large-scale jobs
[ https://issues.apache.org/jira/browse/FLINK-23826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu updated FLINK-23826: Description: This ticket is used to verify the result of FLINK-21110. It should check if large scale jobs' scheduling are working well and the scheduling performance, with a real job running on cluster. The conclusion should include, for a *1 --- all-to-all-connected -->1* job: 1. time of job initialization on master (job received -> scheduling started) 2. time of job scheduling and deployment (scheduling started -> all tasks in INITIALIZATION) 3. time of job restarting on task failover (JM notified about task failure -> all tasks in INITIALIZATION again) 4. master heap memory required was: This ticket is used to verify the result of FLINK-21110. It should check if large scale jobs' scheduling are working well and the scheduling performance, with a real job running on cluster. The conclusion should include, for a *1 ---all-to-all-connected-->1* job: 1. time of job initialization on master (job received -> scheduling started) 2. time of job scheduling and deployment (scheduling started -> all tasks in INITIALIZATION) 3. time of job restarting on task failover (JM notified about task failure -> all tasks in INITIALIZATION again) 4. master heap memory required > Verify optimized scheduler performance for large-scale jobs > --- > > Key: FLINK-23826 > URL: https://issues.apache.org/jira/browse/FLINK-23826 > Project: Flink > Issue Type: Sub-task > Components: Runtime / Coordination >Affects Versions: 1.14.0 >Reporter: Zhu Zhu >Priority: Blocker > Fix For: 1.14.0 > > > This ticket is used to verify the result of FLINK-21110. > It should check if large scale jobs' scheduling are working well and the > scheduling performance, with a real job running on cluster. > The conclusion should include, for a *1 --- all-to-all-connected > -->1* job: > 1. time of job initialization on master (job received -> scheduling started) > 2. time of job scheduling and deployment (scheduling started -> all tasks in > INITIALIZATION) > 3. time of job restarting on task failover (JM notified about task failure -> > all tasks in INITIALIZATION again) > 4. master heap memory required -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-23826) Verify optimized scheduler performance for large-scale jobs
[ https://issues.apache.org/jira/browse/FLINK-23826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu updated FLINK-23826: Description: This ticket is used to verify the result of FLINK-21110. It should check if large scale jobs' scheduling are working well and the scheduling performance, with a real job running on cluster. The conclusion should include, for a *1 ---all-to-all-connected-->1* job: 1. time of job initialization on master (job received -> scheduling started) 2. time of job scheduling and deployment (scheduling started -> all tasks in INITIALIZATION) 3. time of job restarting on task failover (JM notified about task failure -> all tasks in INITIALIZATION again) 4. master heap memory required was: This ticket is used to verify the result of FLINK-21110. It should check if large scale jobs' scheduling are working well and the scheduling performance, with a real job running on cluster. The conclusion should include: 1. time of job initialization on master (job received -> scheduling started) 2. time of job scheduling and deployment (scheduling started -> all tasks in INITIALIZATION) 3. time of job restarting on task failover (JM notified about task failure -> all tasks in INITIALIZATION again) 4. master heap memory required for large scale jobs > Verify optimized scheduler performance for large-scale jobs > --- > > Key: FLINK-23826 > URL: https://issues.apache.org/jira/browse/FLINK-23826 > Project: Flink > Issue Type: Sub-task > Components: Runtime / Coordination >Affects Versions: 1.14.0 >Reporter: Zhu Zhu >Priority: Blocker > Fix For: 1.14.0 > > > This ticket is used to verify the result of FLINK-21110. > It should check if large scale jobs' scheduling are working well and the > scheduling performance, with a real job running on cluster. > The conclusion should include, for a *1 ---all-to-all-connected-->1* > job: > 1. time of job initialization on master (job received -> scheduling started) > 2. time of job scheduling and deployment (scheduling started -> all tasks in > INITIALIZATION) > 3. time of job restarting on task failover (JM notified about task failure -> > all tasks in INITIALIZATION again) > 4. master heap memory required -- This message was sent by Atlassian Jira (v8.3.4#803005)
