[jira] [Commented] (AMBARI-7925) Namenode can not leave safe mode on hdp-2.2 stack

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

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

Hadoop QA commented on AMBARI-7925:
-----------------------------------

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

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

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified test files.

    {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/319//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/319//console

This message is automatically generated.

> Namenode can not leave safe mode on hdp-2.2 stack
> -------------------------------------------------
>
>                 Key: AMBARI-7925
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7925
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 1.7.0
>         Environment: branch-1.7.0 122dae7
> stack HDP-2.2
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 1.7.0
>
>         Attachments: AMBARI-7925.patch
>
>
> Initial analysis:
> First namenode start attempt failed for me. Probably, that caused NN to enter safe mode. After fixing perm gen memory size value, I've tried to start NN again. Our stack scripts seem to move NN out of safe mode on start if needed. But on HDP-2.2 stack, command for doing this is deprecated and fails with a non-zero exit code.
> 2014-10-21 16:33:25,973 - Error while executing command 'start':
> Traceback (most recent call last):
>   File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 122, in execute
>     method(env)
>   File "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/namenode.py", line 46, in start
>     namenode(action="start")
>   File "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/services/HDFS/package/scripts/hdfs_namenode.py", line 60, in namenode
>     only_if=dfs_check_nn_status_cmd #skip when HA not active
>   File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 148, in __init__
>     self.env.run()
>   File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 149, in run
>     self.run_action(resource, action)
>   File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 115, in run_action
>     provider_action()
>   File "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py", line 237, in action_run
>     raise ex
> Fail: Execution of 'su -s /bin/bash - hdfs -c 'export PATH=$PATH:/usr/hdp/current/hadoop-client/bin ; hadoop --config /etc/hadoop/conf dfsadmin -safemode get' | grep 'Safe mode is OFF'' returned 1. DEPRECATED: Use of this script to execute hdfs command is deprecated.
> Instead use the hdfs command for it.
> safemode: Call From 09f.vm/10.77.64.159 to 09f.vm:8020 failed on connection exception: java.net.ConnectException: Connection refused; For more details see:  http://wiki.apache.org/hadoop/ConnectionRefused



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