Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Mon, 7 Oct 2013 18:39:44 +0000 (UTC)
From: "Colin Patrick McCabe (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12672558.1381097577792.27035.1381171184267@arcas>
In-Reply-To: <JIRA.12672558.1381097577792@arcas>
References: <JIRA.12672558.1381097577792@arcas>
Subject: [jira] [Commented] (HDFS-5313) NameNode hangs during startup trying
 to apply OP_ADD_PATH_BASED_CACHE_DIRECTIVE.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Colin Patrick McCabe commented on HDFS-5313:
--------------------------------------------

This code path is changing in HDFS-5096 to fix this and other issues, so we should probably dupe this JIRA to that one.

> NameNode hangs during startup trying to apply OP_ADD_PATH_BASED_CACHE_DIRECTIVE.
> --------------------------------------------------------------------------------
>
>                 Key: HDFS-5313
>                 URL: https://issues.apache.org/jira/browse/HDFS-5313
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: HDFS-4949
>            Reporter: Chris Nauroth
>
> During namenode startup, if the edits contain a {{OP_ADD_PATH_BASED_CACHE_DIRECTIVE}} for an existing file, then the process hangs while trying to apply the op.  This is because of a call to {{FSDirectory#setCacheReplication}}, which calls {{FSDirectory#waitForReady}}, but of course nothing is ever going to mark the directory ready, because it's still in the process of loading.


--
This message was sent by Atlassian JIRA
(v6.1#6144)