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

Hadoop QA commented on AMBARI-13251:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12762647/AMBARI-13251.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/3868//console

This message is automatically generated.

> RU - HDFS_Client restart and hdp-select causes dfs_data_dir_mount.hist to be 
> lost, move file to static location
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-13251
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13251
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.2
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>            Priority: Blocker
>             Fix For: 2.1.2
>
>         Attachments: AMBARI-13251.patch
>
>
> During the Clients group of RU, restarting hdfs_client changes changes the 
> symlink /usr/hdp/current/hadoop-client/ from the old version to the new 
> version.
> Because the Data Dir Mount History file is stored at 
> /etc/hadoop/conf/dfs_data_dir_mount.hist and
> /etc/hadoop/conf symlinks to /usr/hdp/current/hadoop-client/conf 
> it means that the file must be copied to the new location.
> Multiple clients (HDFS, HBase, Hive, YARN, MapReduce, Pig, Slider, Tez) 
> actually end up calling
> {code}
> hdp_select.select("hadoop-client", params.version)
> {code}
> that changes the symlink, so the first one to be ran during RU must copy the 
> file. If DataNode is present, it means that HDFS Client is guaranteed to be 
> there, and from all of those clients it is the first one in the Upgrade Pack.
> During a Rolling Downgrade, the file should already exist in the previous 
> version, and the file is only written to when DataNode is restarted, so we 
> are ok.



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

Reply via email to