You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/07/14 17:39:00 UTC
[jira] [Commented] (BIGTOP-2844) zeppelin charm: spark config
should match zeppelin spark config
[ https://issues.apache.org/jira/browse/BIGTOP-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087664#comment-16087664 ]
ASF GitHub Bot commented on BIGTOP-2844:
----------------------------------------
GitHub user kwmonroe opened a pull request:
https://github.com/apache/bigtop/pull/257
BIGTOP-2844: zeppelin charm: spark config should match zeppelin spark config
See [BIGTOP-2844](https://issues.apache.org/jira/browse/BIGTOP-2844) for details.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/juju-solutions/bigtop bug/BIGTOP-2844/zeppelin-spark-master-test
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/bigtop/pull/257.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 #257
----
commit 71ede9085f23ef052caa7bf6e1df6a2c5b4a7460
Author: Kevin W Monroe <ke...@canonical.com>
Date: 2017-07-13T20:27:35Z
set spark master_url override when reconfiguring zepp
commit ba3f73d8aa85640ea69d82ff5151e9364d62afb3
Author: Kevin W Monroe <ke...@canonical.com>
Date: 2017-07-14T17:25:39Z
cleanup comments; deploy our own spark during the zepp-spark test
----
> zeppelin charm: spark config should match zeppelin spark config
> ---------------------------------------------------------------
>
> Key: BIGTOP-2844
> URL: https://issues.apache.org/jira/browse/BIGTOP-2844
> Project: Bigtop
> Issue Type: Bug
> Components: deployment
> Affects Versions: 1.2.0, 1.2.1
> Reporter: Kevin W Monroe
> Assignee: Kevin W Monroe
> Priority: Minor
> Fix For: 1.3.0
>
>
> The Zeppelin charm deploys spark-client and zeppelin-server roles.
> When zeppelin-server spark config is updated (e.g. we configure it in 'yarn' mode), the spark-client config is not updated. This is fine for jobs submitted through Zeppelin, but if a user attempted to spark-submit on the deployed machine, they may send their job to the wrong master.
> Also, the zeppelin-spark test might stomp on top of a pre-deployed spark charm. Fix this by deploying a test-only copy of the spark charm, run the test, then remove the charm.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)