5954311739
Even we set spark.history.fs.numReplayThreads to a large number, such as 30. The history server still replays logs slowly. We found that, if there is a straggler in a batch of replay tasks, all the other threads will wait for this straggler. In this PR, we create processing to save the logs which are being replayed. So that the replay tasks can execute Asynchronously. It can accelerate the speed to replay logs for history server. No. UT. Closes #25797 from turboFei/SPARK-29043. Authored-by: turbofei <fwang12@ebay.com> Signed-off-by: Marcelo Vanzin <vanzin@cloudera.com> |
||
---|---|---|
.. | ||
benchmarks | ||
src | ||
pom.xml |