hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "star (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-14439) FileNotFoundException thrown in TestEditLogRace when just add a setPermission operation
Date Sat, 20 Apr 2019 00:53:00 GMT

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

star commented on HDFS-14439:
-----------------------------

Not a issue. Function verifyEditlogs load single editlogs segment, which makes it throws such
exception. It happens when mkdir op is in previous segment and verify current segment with
setPermission op.

> FileNotFoundException thrown in TestEditLogRace when just add a setPermission operation
> ---------------------------------------------------------------------------------------
>
>                 Key: HDFS-14439
>                 URL: https://issues.apache.org/jira/browse/HDFS-14439
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: fs
>            Reporter: star
>            Assignee: star
>            Priority: Minor
>
> In TestEditLogRace.Transactions#run, add following code between mkdirs and delete.
>  
> {panel}
> fs.setPermission(dirnamePath, p);
> {panel}
> It will be like. 
> {panel}
> fs.mkdirs(dirnamePath);
> *fs.setPermission(dirnamePath, p);*
> fs.delete(dirnamePath, true);{panel}
> then run test TestEditLogRace#testEditLogRolling, it will throw FileNotFoundException.
> {code:java}
> java.io.FileNotFoundException: cannot find /thr-291-dir-2
> at org.apache.hadoop.hdfs.server.namenode.FSDirectory.resolveLastINode(FSDirectory.java:1524)
> at org.apache.hadoop.hdfs.server.namenode.FSDirAttrOp.unprotectedSetPermission(FSDirAttrOp.java:264)
> at org.apache.hadoop.hdfs.server.namenode.FSEditLogLoader.applyEditLogOp(FSEditLogLoader.java:656)
> at org.apache.hadoop.hdfs.server.namenode.FSEditLogLoader.loadEditRecords(FSEditLogLoader.java:287)
> at org.apache.hadoop.hdfs.server.namenode.FSEditLogLoader.loadFSEdits(FSEditLogLoader.java:182)
> at org.apache.hadoop.hdfs.server.namenode.FSEditLogLoader.loadFSEdits(FSEditLogLoader.java:159)
> at org.apache.hadoop.hdfs.server.namenode.TestEditLogRace.verifyEditLogs(TestEditLogRace.java:293)
> at org.apache.hadoop.hdfs.server.namenode.TestEditLogRace.testEditLogRolling(TestEditLogRace.java:258)
> {code}
> It happens when verifing edit logs and finds the target dir does not exits. Any one could
help figure out whether it makes sense or what makes it behaving that way?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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


Mime
View raw message