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

Andrew Wang updated HDFS-5845:
------------------------------

    Attachment: hdfs-5845-1.patch

Patch attached. This was pretty simple, but requires taking the FSN writelock 
on the 2NN since we have a bunch of write lock asserts in CacheManager. I think 
this is okay since we already do this in the SbNN, but someone should weigh in 
if this isn't okay.

{{diff -w}} helps with reviewing the test change, since I needed to indent a 
test by one.

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

Reply via email to