We got lots of error log as follows due to mismatch of the length between plan metrics and stage metrics:
2023-04-27T07:08:05.745787Z ERROR tokio-runtime-worker ThreadId(07) ballista_scheduler::display: Fail to combine stage metrics to plan for stage [5H4NLbc/3], plan metrics array size 5 does not equal to the stage metrics array size 4
The metrics length of stage is always one less than the one of plan.
Which issue does this PR close?
Closes #763.
We got lots of error log as follows due to mismatch of the length between plan metrics and stage metrics:
2023-04-27T07:08:05.745787Z ERROR tokio-runtime-worker ThreadId(07) ballista_scheduler::display: Fail to combine stage metrics to plan for stage [5H4NLbc/3], plan metrics array size 5 does not equal to the stage metrics array size 4
The metrics length of stage is always one less than the one of plan.
Rationale for this change
It's caused by #687.
What changes are included in this PR?
Are there any user-facing changes?