b5fab42604
### What changes were proposed in this pull request? LifecycleManager respond to RegisterShuffle with max epoch PartitionLocation. ### Why are the changes needed? Newly spun up executors in a Spark job will still get the partitionLocations with the minEpoch of the celeborn lost worker. These executors will fail to connect to the lost worker and then call into revive to get the latest PartitionLocation for a given partitionId in `ChangePartitionManager.getLatestPartition()`. Return with max epoch can reduce such revive requests. ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? UT. Closes #3135 from zaynt4606/clb1822. Authored-by: zhengtao <shuaizhentao.szt@alibaba-inc.com> Signed-off-by: Shuang <lvshuang.xjs@alibaba-inc.com> |
||
|---|---|---|
| .. | ||
| flink-it | ||
| kubernetes-it | ||
| mr-it | ||
| spark-it | ||
| tez-it | ||