GitHub user zenglinxi0615 opened a pull request:
https://github.com/apache/spark/pull/18430
[SPARK-21223]:Thread-safety issue in FsHistoryProvider
## What changes were proposed in this pull request?
fix the Thread-safety issue in FsHistoryProvider
Currently, Spark HistoryServer use a HashMap named fileToAppInfo in class
FsHistoryProvider to store the map of eventlog path and attemptInfo.
When use ThreadPool to Replay the log files in the list and merge the list
of old applications with new ones, multi thread may update fileToAppInfo at the
same time, which may cause Thread-safety issues.
(Please fill in changes proposed in this fix)
## How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration
tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise,
remove this)
Please review http://spark.apache.org/contributing.html before opening a
pull request.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zenglinxi0615/spark master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/18430.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #18430
----
commit d2b3c960012403fcc9be6fbd33f74f395d879f9d
Author: æ¾æ西 <[email protected]>
Date: 2017-06-27T07:29:44Z
[SPARK-21223]:Thread-safety issue in FsHistoryProvider
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
