hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HDFS-5313) NameNode hangs during startup trying to apply OP_ADD_PATH_BASED_CACHE_DIRECTIVE.
Date Wed, 16 Oct 2013 19:13:43 GMT

     [ https://issues.apache.org/jira/browse/HDFS-5313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Nauroth resolved HDFS-5313.
---------------------------------

    Resolution: Duplicate
      Assignee: Chris Nauroth

I've confirmed that HDFS-5096 fixes this bug.

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

Mime
View raw message