ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-19222) %livy interpreter gives 400 HttpClientError due to spark.master property present in livy-spark-blacklist
Date Mon, 19 Dec 2016 10:07:58 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-19222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15760765#comment-15760765
] 

Hudson commented on AMBARI-19222:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6254 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6254/])
AMBARI-19222 %livy interpreter gives 400 HttpClientError due to (renjith.kamath: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=fce9d6e090c9433f5783871aab73cdb3e16c9335])
* (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py


> %livy interpreter gives 400 HttpClientError due to spark.master property present in livy-spark-blacklist
> --------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-19222
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19222
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Prabhjyot Singh
>            Assignee: Prabhjyot Singh
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-19222_branch-2.5-v1.patch
>
>
> spark.master should not be overridden because we want to use livy's own default = cluster
not overridden by the user via zeppelin. so it should be present in the blacklist if I understand
right. zeppelin should stop specifying livy.spark.master in the livy interpreter in case it
does so now.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message