Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BFC4410FCA for ; Tue, 28 Jan 2014 23:53:17 +0000 (UTC) Received: (qmail 39796 invoked by uid 500); 28 Jan 2014 23:53:12 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 39636 invoked by uid 500); 28 Jan 2014 23:53:09 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 39563 invoked by uid 99); 28 Jan 2014 23:53:08 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Jan 2014 23:53:08 +0000 Date: Tue, 28 Jan 2014 23:53:07 +0000 (UTC) From: "Suresh Srinivas (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: 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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-5845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13884927#comment-13884927 ] Suresh Srinivas commented on HDFS-5845: --------------------------------------- [~andrew.wang], I am marking this as blocker for 2.3.0. > 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 > > 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)