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

Hudson commented on AMBARI-21572:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1765 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1765/])
AMBARI-21572. Spark configuration mismatch post express upgrade (adoroszlai: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9e0a7fbe246106f729fdabcca633fe509b5491bd])
* (edit) 
ambari-server/src/main/resources/stacks/BigInsights/4.2.5/upgrades/nonrolling-upgrade-to-hdp-2.6.xml
* (edit) 
ambari-server/src/main/resources/stacks/BigInsights/4.2.5/upgrades/config-upgrade.xml


> Spark configuration mismatch post express upgrade
> -------------------------------------------------
>
>                 Key: AMBARI-21572
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21572
>             Project: Ambari
>          Issue Type: Bug
>          Components: service-advisor
>    Affects Versions: 2.5.2
>            Reporter: Eric Yang
>            Assignee: Doroszlai, Attila
>             Fix For: 2.5.2
>
>         Attachments: AMBARI-21572.patch
>
>
> During upgrade from IOP 4.2.x to HDP 2.6.2, there is a warning with the spark 
> property spark.yarn.archive the value is:
> hdfs:///iop/apps/4.2.5.0-0000/spark2/spark2-iop-yarn-archive.tar.gz prior to 
> the EU
> hdfs:///*hdp*/apps/4.2.5.0-0000/spark2/spark2-iop-yarn-archive.tar.gz post EU
> If this property isn't used by HDP it should be deleted during the stack 
> upgrade. If it is used by HDP then the version number 4.2.5.0-0000 should be 
> updated to a param.
> Spark2 alert had issues connecting to the thrift server post migration where 
> it tried to ping port 4038 (defined by spark.thriftserver.ui.port, carried 
> over from IOP before migration) while the process really was running on 4040. 
> I got the alerts working again by updating *spark.thriftserver.ui.port* to 
> 4040.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to