[jira] [Commented] (AMBARI-9485) RU - Add more debugging information to HDFS prepare and finalize steps

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-9485:
-----------------------------------

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

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/1588//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/1588//console

This message is automatically generated.

> 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)