[
https://issues.apache.org/jira/browse/HDFS-5845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885045#comment-13885045
]
Hadoop QA commented on HDFS-5845:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12625772/hdfs-5845-1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-hdfs-project/hadoop-hdfs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/5975//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/5975//console
This message is automatically generated.
> 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)
