[ 
https://issues.apache.org/jira/browse/AMBARI-10976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jonathan Hurley resolved AMBARI-10976.
--------------------------------------
    Resolution: Fixed

> HDP-2.2 To HDP-2.3 Upgrade Pre-Upgrade Checks
> ---------------------------------------------
>
>                 Key: AMBARI-10976
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10976
>             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
>
>
> Create the new pre-requisite checks for HDP 2.2 to HDP 2.3 rolling upgrades. 
> This includes:
> - Ensuring the cluster stack version is at HDP 2.2 and is moving to HDP 2.3
> - Ensure that YARN ResourceManager HA is enabled (Warning if not enabled)
> - Enable client retry properties for HDFS, Hive, and Oozie. These properties 
> are not included by default, so you might need to add them to the site files.
> -- For HDFS, set dfs.client.retry.policy.enabled to true in hdfs-site.xml on 
> all nodes with HDFS services.
> -- For Hive, specify hive.metastore.failure.retries and 
> hive.metastore.client.connect.retry.delay in hive-site.xml (for example,
> /usr/hdp/2.2.0.0-2041/hive/conf/hive-site.xml). The default value for retries 
> is 24; the default for retry delay is 5s.
> -- For Oozie, export OOZIE_CLIENT_OPTS="${OOZIE_CLIENT_OPTS} 
> -Doozie.connection.retry.count=<number of retries>" in oozie-env.sh (for 
> example, /usr/hdp/2.2.0.0-2041/oozie/conf/oozie-env.sh). A typical value for 
> number of retries is 5.
> - Enable work-preserving ResourceManager/NodeManager/TimelineServer restart 
> in the yarn-site.xml file for each node. For more information, see 
> Work-Preserving Restart in the YARN Resource Management Guide.
> - Make sure HiveServer2 is configured for rolling upgrade. Set or confirm the 
> following server-side properties:
> -- Set hive.server2.support.dynamic.service.discovery to true
> -- Set hive.zookeeper.quorum to a comma-separated list of ZooKeeper host:port 
> pairs in the Zookeeper ensemble (e.g. host1:port1, host2:port2, host3:port3). 
> By default this value is blank.
> -- Add the hive.zookeeper.session.timeout property to the hive-site.xml file 
> (if necessary), and specify the length of time that ZooKeeper will wait to 
> hear from HiveServer2 before closing the client connection. The default value 
> is 60 seconds.
> -- Set hive.server2.zookeeper.namespace to the value for the root namespace 
> on ZooKeeper. (The root namespace is the parent node in ZooKeeper used by 
> HiveServer2 when supporting dynamic service discovery.) Each HiveServer2 
> instance with dynamic service discovery enabled will create a znode within 
> this namespace. The default value is hiveserver2.
> - Tez Configurations
> -- tez.lib.uris (in the tez-site.xml file) should contain only a single value 
> pointing to a version-specific Tez tarball file. For 2.2 installations, the 
> Tez app jars are in /hdp/apps/${hp.version}
> -- Set tez.use.cluster.hadoop-libs to false. (If true, the deployment will 
> expect Hadoop jar files to be available on all nodes.



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

Reply via email to