Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Wed, 29 Jan 2014 23:44:15 +0000 (UTC)
From: "Andrew Wang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12691939.1390953002863.6711.1391039055513@arcas>
In-Reply-To: <JIRA.12691939.1390953002863@arcas>
References: <JIRA.12691939.1390953002863@arcas>
Subject: [jira] [Commented] (HDFS-5845) SecondaryNameNode dies when
 checkpointing with cache pools
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrew Wang commented on HDFS-5845:
-----------------------------------

I'll also note that I bumped the timeout on that seemingly unrelated test since it flaked twice for me at 30s.

> SecondaryNameNode dies when checkpointing with cache pools
> ----------------------------------------------------------
>
>                 Key: HDFS-5845
>                 URL: https://issues.apache.org/jira/browse/HDFS-5845
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.3.0
>            Reporter: Andrew Wang
>            Assignee: Andrew Wang
>            Priority: Blocker
>              Labels: caching
>         Attachments: hdfs-5845-1.patch
>
>
> The SecondaryNameNode clears and reloads its FSNamesystem when doing checkpointing. However, FSNamesystem#clear does not clear CacheManager state during this reload. This leads to an error like the following:
> {noformat}
> org.apache.hadoop.fs.InvalidRequestException: Cache pool pool1 already exists.
> {noformat}


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)