[
https://issues.apache.org/jira/browse/AMBARI-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-9160:
------------------------------------
Attachment: AMBARI-9160.patch
> Hadoop Clients Should Update All Clients During Rolling Upgrade
> ---------------------------------------------------------------
>
> Key: AMBARI-9160
> URL: https://issues.apache.org/jira/browse/AMBARI-9160
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Fix For: 2.0.0
>
> Attachments: AMBARI-9160.patch
>
>
> During a rolling upgrade, service components and clients call {{hdp-select}}
> to set the new version and update symlinks in {{/usr/hdp/current}}.
> There is a problem in that {{/usr/hdp/current/hadoop-client}} may never be
> run if there are non-HDFS/YARN/MapR clients installed on a host. Essentially,
> components always call
> {noformat}
> hdp-select set oozie-client 2.2.1.0-1234
> {noformat}
> Where the component name is scoped correctly (falcon-client, etc)
> {{/usr/hdp/current/hadoop-client}} however does not have an associated
> client. Therefore, the
> {{<group name="CLIENTS" title="Client Components">}} group in the upgrade
> pack should call the following:
> {noformat}
> hdp-select set client 2.2.1.0-1234
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
