You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2016/01/25 18:43:40 UTC
[jira] [Commented] (AMBARI-14789) Spark Thrift Server component
does not start after EU from HDP-2.3.4 to HDP-2.4.0 with umask 027
[ https://issues.apache.org/jira/browse/AMBARI-14789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115624#comment-15115624 ]
Hudson commented on AMBARI-14789:
---------------------------------
FAILURE: Integrated in Ambari-branch-2.2 #241 (See [https://builds.apache.org/job/Ambari-branch-2.2/241/])
AMBARI-14789. Spark Thrift Server component does not start after EU from (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=cf059bf134091ac1d77c4a102a1c2a18f4196c52])
* ambari-server/src/test/python/stacks/2.2/SPARK/test_job_history_server.py
* ambari-server/src/main/resources/common-services/SPARK/1.2.0.2.2/package/scripts/setup_spark.py
* ambari-server/src/test/python/stacks/2.2/SPARK/test_spark_client.py
* ambari-server/src/test/python/stacks/2.3/SPARK/test_spark_thrift_server.py
* ambari-server/src/main/resources/common-services/SPARK/1.2.0.2.2/package/scripts/params.py
> Spark Thrift Server component does not start after EU from HDP-2.3.4 to HDP-2.4.0 with umask 027
> ------------------------------------------------------------------------------------------------
>
> Key: AMBARI-14789
> URL: https://issues.apache.org/jira/browse/AMBARI-14789
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.2.1
>
> Attachments: AMBARI-14789.patch
>
>
> **Steps:**
> * Install HDP 2.3.4.0 cluster with Ambari 2.2.1 with customized service users
> * Perform Express Upgrade to 2.4.0.0-128
> * Observe the status of STS component
> **Result:**
> STS shows down on all hosts
> I tried to find some errors in the log but nothing much in /var/log/spark
> directory on the hosts to indicate what could be wrong
> Writing this as a new Jira because my impression was that this test was
> failing earlier due to which is now fixed)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)