[
https://issues.apache.org/jira/browse/HADOOP-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531122
]
Konstantin Shvachko commented on HADOOP-1935:
---------------------------------------------
I'd add that file does not exist. Also formatting should be corrected, long
line.
{code}
NameNode.stateChangeLog.warn("DIR* NameSystem.internalReleaseCreate: "
+ "attempt to release a create lock on "
+ src.toString() + " file does not exist.");
{code}
> NullPointerException in internalReleaseCreate
> ---------------------------------------------
>
> Key: HADOOP-1935
> URL: https://issues.apache.org/jira/browse/HADOOP-1935
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.15.0
> Reporter: Konstantin Shvachko
> Assignee: dhruba borthakur
> Priority: Blocker
> Fix For: 0.15.0
>
> Attachments: npePendingCreate.patch
>
>
> The exception occurs during abandonFileInProgress().
> {code}
> 07/09/21 13:59:28 ERROR fs.FSNamesystem: java.lang.NullPointerException
> at
> org.apache.hadoop.dfs.FSNamesystem.internalReleaseCreate(FSNamesystem.java:1494)
> at org.apache.hadoop.dfs.FSNamesystem.access$100(FSNamesystem.java:50)
> at
> org.apache.hadoop.dfs.FSNamesystem$Lease.releaseLocks(FSNamesystem.java:1385)
> at
> org.apache.hadoop.dfs.FSNamesystem$LeaseMonitor.run(FSNamesystem.java:1447)
> at java.lang.Thread.run(Thread.java:595)
> {code}
> My guess is that the client sends abandonFileInProgress() after create(),
> which timed out and was not executed by the name-node.
> That is why dir.getFileINode(src) returns null in internalReleaseCreate().
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
