[
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 *10000 --- all-to-all-connected -->10000*
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 *10000 ---all-to-all-connected-->10000*
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 *10000 --- all-to-all-connected
> -->10000* 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)
