hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uma Maheswara Rao G (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-11695) [SPS]: Namenode failed to start while loading SPS xAttrs from the edits log.
Date Tue, 25 Apr 2017 06:30:05 GMT

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

Uma Maheswara Rao G commented on HDFS-11695:

Thanks [~surendrasingh] for reporting it. Can you explain me the scenario when its coming?

I think you are right. We can reproduce this case in the following case:
 call satisfyStoragePolicy on one directory first. Then try calling satisfy policy on parent
directory, here it will restricts to satisfy policy  as sub directory already has Xattr. But
you can explain the case how you got while starting NN.

Do you want to fix it? Let me know if any help

> [SPS]: Namenode failed to start while loading SPS xAttrs from the edits log.
> ----------------------------------------------------------------------------
>                 Key: HDFS-11695
>                 URL: https://issues.apache.org/jira/browse/HDFS-11695
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>    Affects Versions: HDFS-10285
>            Reporter: Surendra Singh Lilhore
>            Assignee: Surendra Singh Lilhore
>            Priority: Blocker
>         Attachments: fsimage.xml
> {noformat}
> 2017-04-23 13:27:51,971 ERROR org.apache.hadoop.hdfs.server.namenode.NameNode: Failed
to start namenode.
> java.io.IOException: Cannot request to call satisfy storage policy on path /ssl, as this
file/dir was already called for satisfying storage policy.
>         at org.apache.hadoop.hdfs.server.namenode.FSDirAttrOp.unprotectedSatisfyStoragePolicy(FSDirAttrOp.java:511)
>         at org.apache.hadoop.hdfs.server.namenode.FSDirXAttrOp.unprotectedSetXAttrs(FSDirXAttrOp.java:284)
>         at org.apache.hadoop.hdfs.server.namenode.FSEditLogLoader.applyEditLogOp(FSEditLogLoader.java:918)
>         at org.apache.hadoop.hdfs.server.namenode.FSEditLogLoader.loadEditRecords(FSEditLogLoader.java:241)
>         at org.apache.hadoop.hdfs.server.namenode.FSEditLogLoader.loadFSEdits(FSEditLogLoader.java:150)
> {noformat}

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message