zhli1142015 edited a comment on pull request #28769: URL: https://github.com/apache/spark/pull/28769#issuecomment-641752768
> Then how about capture the exception and ask the user to increase the related configuration or try loading the page again? Because there is disk space limitation, we can only mitigate it by stopping service and manually cleaning disk cache, this is a little annoying. > What is the benefit of this PR to users? I think the cause of issue is resource leaking (file handle on Windows which prevent releasing space by `HistoryServerDiskManager` ) caused by race condition, my pr is trying to fix this. we actually use spark history server as long running service to provide diagnostic experience to others. The benefit to us is we don't need to stop service and manually restart HS after some period. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org
