GitHub user zsxwing opened a pull request:
https://github.com/apache/spark/pull/3721
WriteAheadLogBasedBlockHandler improvement
1. Move the block store work to a separate thread pool. IO work usually
runs longer than CPU work. Running IO work in `Implicits.global` may block
other work that want to run in `Implicits.global`.
2. Use `Future.zip` instead of `Future.flatMap`(for-loop). `zip` implies
these two Futures will run concurrently, while `flatMap` usually means one
Future depends on the other one.
3. Fix a unit test in `ReceivedBlockTrackerSuite` which may fail
occasionally.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zsxwing/spark SPARK-4873
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/3721.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 #3721
----
commit 860f3a2b1d30f4640e1be16cae9609bb5e394c40
Author: zsxwing <zsxw...@gmail.com>
Date: 2014-12-17T09:54:53Z
WriteAheadLogBasedBlockHandler improvement
----
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
