GitHub user JoshRosen opened a pull request:
https://github.com/apache/spark/pull/1680
[WIP] [SPARK-2764] Simplify daemon.py process structure
Curently, daemon.py forks a pool of numProcessors subprocesses, and those
processes fork themselves again to create the actual Python worker processes
that handle data.
I think that this extra layer of indirection is unnecessary and adds a lot
of complexity. This commit attempts to remove this middle layer of
subprocesses by launching the workers directly from daemon.py.
See https://github.com/mesos/spark/pull/563 for the original PR that added
daemon.py, where I raise some issues with the current design.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/JoshRosen/spark pyspark-daemon
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/1680.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 #1680
----
commit dda5dd7d6895acfbfef9a7c61d744ee6f279fbe3
Author: Josh Rosen <[email protected]>
Date: 2014-07-31T03:50:32Z
[WIP] [SPARK-2764] Simplify daemon.py process structure.
Curently, daemon.py forks a pool of numProcessors subprocesses, and those
processes fork themselves again to create the actual Python worker processes
that handle data.
I think that this extra layer of indirection is unnecessary and adds a lot
of
complexity. This commit attemps to remove this middle layer of subprocesses
by launching the workers directly from daemon.py.
See https://github.com/mesos/spark/pull/563 for the original PR that added
daemon.py, where I raise some issues with the current design.
----
---
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.
---
