[
https://issues.apache.org/jira/browse/HDFS-5388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated HDFS-5388:
--------------------------------
Attachment: HDFS-5388.1.patch
I just noticed the problem this morning after my namenode did a checkpoint and
I restarted. This was introduced in HDFS-5096. I'm attaching a fix. After I
applied this patch, I was able to load my fsimage and start my namenode
successfully.
[~cmccabe] and [~andrew.wang], does this look good?
> Loading fsimage fails to find cache pools during namenode startup.
> ------------------------------------------------------------------
>
> Key: HDFS-5388
> URL: https://issues.apache.org/jira/browse/HDFS-5388
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: HDFS-4949
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Attachments: HDFS-5388.1.patch
>
>
> The namenode fails during startup due to a check that a cache entry does not
> refer to a non-existent pool. We need to make a small change to this logic.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
