[
https://issues.apache.org/jira/browse/AMBARI-9485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14309713#comment-14309713
]
Hudson commented on AMBARI-9485:
--------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #1708 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/1708/])
AMBARI-9485. RU - Add more debugging information to HDFS prepare and finalize
steps (alejandro) (afernandez:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=21bf7c330938b575a943fb90d837fd2787aa0e15)
*
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode_upgrade.py
> RU - Add more debugging information to HDFS prepare and finalize steps
> ----------------------------------------------------------------------
>
> Key: AMBARI-9485
> URL: https://issues.apache.org/jira/browse/AMBARI-9485
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Alejandro Fernandez
> Assignee: Alejandro Fernandez
> Fix For: 2.0.0
>
> Attachments: AMBARI-9485.patch
>
>
> Add more debugging information for HDFS prepare and finalize steps.
> Prepare:
> 1. With HA setup, the current code requires the NameNode NOT in safemode when
> starting RU.
> 2. With non-HA setup, the current code requires the NameNode in safemode when
> start RU.
> The reason is that for non-HA setup, we need to do an extra checkpoint in the
> single NN (by calling saveNamespace), which requires the NN to be in safemode
> (to avoid namespace modification during the checkpoint). But for HA-setup,
> the checkpoint is done by the standby NN, thus we do not need to put the
> active NN into the safemode and in this way we can avoid service downtime.
> We need to log what the original state is.
> Finalize:
> This has a confusing message related to
> https://issues.apache.org/jira/secure/attachment/12679263/HDFS-7340.001.patch
> {code}
> [root@c6404 ~]# su - hdfs -c 'hdfs dfsadmin -rollingUpgrade query'
> QUERY rolling upgrade ...
> Proceed with rolling upgrade:
> Block Pool ID: BP-819970438-192.168.64.104-1423091248521
> Start Time: Thu Feb 05 01:15:16 UTC 2015 (=1423098916798)
> Finalize Time: <NOT FINALIZED>
> [root@c6404 ~]# su - hdfs -c 'hdfs dfsadmin -rollingUpgrade finalize'
> FINALIZE rolling upgrade ...
> There is no rolling upgrade in progress or rolling upgrade has already been
> finalized.
> [root@c6404 ~]# su - hdfs -c 'hdfs dfsadmin -rollingUpgrade query'
> QUERY rolling upgrade ...
> There is no rolling upgrade in progress or rolling upgrade has already been
> finalized.
> {code}
> This means that the finalize did happen.
> We should run another "hdfs dfsadmin -rollingUpgrade query" after finalize to
> ensure this happened.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
