ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-9461) Issue with namenode format
Date Tue, 03 Feb 2015 22:21:35 GMT

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

Hudson commented on AMBARI-9461:
--------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #1679 (See [https://builds.apache.org/job/Ambari-trunk-Commit/1679/])
AMBARI-9461 Issue with namenode format (dlysnichenko) (dlysnichenko: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d128a0dc6f3298f613435762aecda5cce606ce4b)
* ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py
* ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py
* ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/files/checkForFormat.sh
* ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params.py


> Issue with namenode format
> --------------------------
>
>                 Key: AMBARI-9461
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9461
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9461.patch
>
>
> Appears to be a bug:
> checkForFormat.sh looks for a "${mark_dir}" to determine if the namenode dir is formatted.
> But "${mark_dir}" seems to be hardcoded to /var/lib/hdfs/namenode/formatted
> when it should instead use {dfs.namenode.data.dir}/formatted/.
> That results in:
> …/formatted/ never being created (it tries but the parent dir /var/lib/hdfs/namenode
doesn’t exist so it can’t)
> …/formatted/ not being checked on cluster build
> I’ve temporarily hacked around the issue by applying a symbolic link before Ambari
automation starts:
> mkdir /hadoop/hdfs; ln -s /hadoop/hdfs /var/lib/
> (where /hadoop/hdfs is the base of all hdfs dirs. Result in /hadoop/hdfs/namenode/formatted
being available at /var/lib/hdfs/namenode/formatted)



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

Mime
View raw message