GitHub user reactormonk opened a pull request:
https://github.com/apache/spark/pull/9507
[SPARK-11539] debian packaging
A few questions that could simplify the package:
a) does spark-env.sh need to be a bash script? With VAR=value only I could
use EnvironmentFile= from systemd and start the daemons directly.
b) is it useful to have more than one slave per machine in production? I
just saw the slave startup script implements that, so I followed along.
c) Will spark have a problem that it can't delete the work directly? I
currently symlinked it to /var/lib/apache-spark/.
On the build itself:
d) How do I find the absolute base directory? Currently I'm running
assembly/debian:packageBin and using baseDirectory.value / ".."
e) A nice way to write something into the RELEASE file.
Restrictions:
- Only supports systemd. Feel free to add some more.
- Can only build when dpkg-deb is available. I can't load JDeb because of
version conflicts with sbt-pom-reader.
- Not really "batteries included" because it tries to connect to localhost,
where it should connect to `hostname`.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/reactormonk/spark debian-packaging
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/9507.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 #9507
----
commit 7310df7f1e7b1b3c34ce997b1034cdcc444291ef
Author: Simon Hafner <[email protected]>
Date: 2015-11-05T21:31:32Z
[SPARK-11539] debian packaging
----
---
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]
