ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-11006) YARN Upgrade Pack For HDP-2.2 To HDP-2.3
Date Fri, 08 May 2015 19:34:01 GMT

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

Hudson commented on AMBARI-11006:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #2553 (See [https://builds.apache.org/job/Ambari-trunk-Commit/2553/])
AMBARI-11006 - YARN Upgrade Pack For HDP-2.2 To HDP-2.3 (part2) (jonathanhurley) (jhurley:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=41a41e64b0bfe5c14479555c95dcab2680f25f1f)
* ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/ConfigureAction.java


> YARN Upgrade Pack For HDP-2.2 To HDP-2.3
> ----------------------------------------
>
>                 Key: AMBARI-11006
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11006
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.1.0
>
>
> h2. Support YARN ResourceManager HA
> If High Availability is not enabled for the YARN ResourceManager, shut down the ResourceManager
process, switch to the newer version, and start the ResourceManager process:
> {noformat}
> su - yarn -c "/usr/hdp/current/hadoop-yarn-resourcemanager/sbin/ yarn-daemon.sh stop
resourcemanager"
> hdp-select set hadoop-yarn-resourcemanager 2.2.4.0-2633
> su - yarn -c "/usr/hdp/current/hadoop-yarn-resourcemanager/sbin/ yarn-daemon.sh start
resourcemanager"
> {noformat}
> If High Availability is enabled for the YARN ResourceManager, you’ll need to upgrade
both ResourceManager processes, starting with the standby process. This is similar to the
process you used for the NameNode pair:
> 1. Upgrade the standby process
> 2. Failover from active to standby
> 3. Upgrade the new standby process (formerly the active process)
> In the following instructions, RM1 refers to the currently active ResourceManager. RM2
refers to the current standby ResourceManager.
> 1. Shut down the standby Resource Manager (RM2), switch to the newer version, and start
RM2:
> {noformat}
> su - yarn -c "/usr/hdp/current/hadoop-yarn-resourcemanager/sbin/ yarn-daemon.sh stop
resourcemanager"
> hdp-select set hadoop-yarn-resourcemanager 2.2.4.0-2633
> su - yarn -c "/usr/hdp/current/hadoop-yarn-resourcemanager/sbin/ yarn-daemon.sh start
resourcemanager"
> {noformat}
> RM2 will start, and will become the standby ResourceManager.
> 2. To switch the standby ResourceManager, stop the active ResourceManager:
> su - yarn -c "/usr/hdp/current/hadoop-yarn-resourcemanager/sbin/ yarn-daemon.sh stop
resourcemanager"
> 3. Shut down the new standby ResourceManager (RM1), switch to the new version, and start
RM1:
> {noformat}
> su - yarn -c "/usr/hdp/current/hadoop-yarn-resourcemanager/sbin/ yarn-daemon.sh stop
resourcemanager"
> hdp-select set hadoop-yarn-resourcemanager 2.2.4.0-2633
> su - yarn -c "/usr/hdp/current/hadoop-yarn-resourcemanager/sbin/ yarn-daemon.sh start
resourcemanager"
> {noformat}
> RM1 will start and become the standby ResourceManager. For version info, see http://<node-name>:8088/cluster/cluster.
> h2. YARN Configuration Changes
> |YARN|	|-|	|-|	|yarn.node-labels.enabled|	|FALSE|	|yarn-site.xml|	|Y|	|No|
> |YARN|	|-|	|-|	|yarn.timeline-service.recovery.enabled|	|TRUE|	|yarn-site.xml|	|Y|	|No|
> |YARN|	|-|	|-|	|yarn.timeline-service.state-store-class|	|org.apache.hadoop.yarn.server.timeline.recovery.LeveldbTimelineStateStore|
|yarn-site.xml|	|Y|	|No|
> |YARN|	|-|	|-|	|yarn.timeline-service.leveldb-state-store.path|	|<the same as the
default of "yarn.timeline-service.leveldb-timeline-store.path">|	|yarn-site.xml|	|Y|	|No|
> 							
> |MapReduce|	|mapreduce.job.speculative.speculativecap|	|mapred-site.xml|	|mapreduce.job.speculative.speculative-cap-running-tasks|
|0.1|	|mapred-site.xml|	|Y|	|No|
> |MapReduce|	|mapreduce.task.tmp.dir|	mapred-site.xml|	|<Deleted>|	|-|	|mapred-site.xml|
> |MapReduce|	|-|	|-|	|mapreduce.fileoutputcommitter.algorithm.version|	 |1|	|mapred-site.xml|
|Y|	|No|



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

Mime
View raw message