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/08/03 14:46: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=16112845#comment-16112845 ] 

ASF GitHub Bot commented on BIGTOP-2844:
----------------------------------------

Github user kwmonroe commented on the issue:

    https://github.com/apache/bigtop/pull/257
  
    This has been working well for a few weeks now.  Merging.


> 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)