You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Konstantin Shvachko (JIRA)" <ji...@apache.org> on 2007/09/22 02:41:50 UTC
[jira] Created: (HADOOP-1935) NullPointerException in
internalReleaseCreate
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
Fix For: 0.15.0
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.
[jira] Updated: (HADOOP-1935) NullPointerException in
internalReleaseCreate
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-1935:
-------------------------------------
Status: Patch Available (was: Open)
> 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: npePendingCreate2.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.
[jira] Updated: (HADOOP-1935) NullPointerException in
internalReleaseCreate
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-1935:
-------------------------------------
Attachment: (was: npePendingCreate3.patch)
> 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: npePendingCreate2.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.
[jira] Commented: (HADOOP-1935) NullPointerException in
internalReleaseCreate
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531223 ]
Hadoop QA commented on HADOOP-1935:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12366796/npePendingCreate3.patch
against trunk revision r580487.
@author +1. The patch does not contain any @author tags.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new compiler warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests +1. The patch passed core unit tests.
contrib tests +1. The patch passed contrib unit tests.
Test results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/849/testReport/
Findbugs warnings: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/849/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/849/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/849/console
This message is automatically generated.
> 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: npePendingCreate3.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.
[jira] Updated: (HADOOP-1935) NullPointerException in
internalReleaseCreate
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-1935:
-------------------------------------
Attachment: (was: npePendingCreate2.patch)
> 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: npePendingCreate3.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.
[jira] Commented: (HADOOP-1935) NullPointerException in
internalReleaseCreate
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531212 ]
Hadoop QA commented on HADOOP-1935:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12366794/npePendingCreate2.patch
against trunk revision r580487.
@author +1. The patch does not contain any @author tags.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new compiler warnings.
findbugs -1. The patch appears to introduce 1 new Findbugs warnings.
core tests +1. The patch passed core unit tests.
contrib tests +1. The patch passed contrib unit tests.
Test results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/848/testReport/
Findbugs warnings: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/848/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/848/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/848/console
This message is automatically generated.
> 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: npePendingCreate2.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.
[jira] Updated: (HADOOP-1935) NullPointerException in
internalReleaseCreate
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-1935:
-------------------------------------
Attachment: (was: npePendingCreate.patch)
> 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: npePendingCreate2.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.
[jira] Updated: (HADOOP-1935) NullPointerException in
internalReleaseCreate
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-1935:
-------------------------------------
Status: Patch Available (was: Open)
> 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: npePendingCreate3.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.
[jira] Commented: (HADOOP-1935) NullPointerException in
internalReleaseCreate
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531584 ]
Hudson commented on HADOOP-1935:
--------------------------------
Integrated in Hadoop-Nightly #256 (See [http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Nightly/256/])
> 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: npePendingCreate3.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.
[jira] Commented: (HADOOP-1935) NullPointerException in
internalReleaseCreate
Posted by "Konstantin Shvachko (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Assigned: (HADOOP-1935) NullPointerException in
internalReleaseCreate
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur reassigned HADOOP-1935:
----------------------------------------
Assignee: dhruba borthakur
> 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
>
>
> 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.
[jira] Commented: (HADOOP-1935) NullPointerException in
internalReleaseCreate
Posted by "Konstantin Shvachko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531420 ]
Konstantin Shvachko commented on HADOOP-1935:
---------------------------------------------
+1
> 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: npePendingCreate3.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.
[jira] Updated: (HADOOP-1935) NullPointerException in
internalReleaseCreate
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-1935:
-------------------------------------
Status: Patch Available (was: Open)
I am submitting this patch so that HadoopQA gets to run all tests. Have incorporated all review comments. Konstantin: if you care to review it once more, please do so.
> 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: npePendingCreate2.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.
[jira] Updated: (HADOOP-1935) NullPointerException in
internalReleaseCreate
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-1935:
-------------------------------------
Attachment: npePendingCreate3.patch
Fixed findbugs warning found in earlier patch.
> 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: npePendingCreate2.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.
[jira] Updated: (HADOOP-1935) NullPointerException in
internalReleaseCreate
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-1935:
-------------------------------------
Attachment: npePendingCreate.patch
> 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.
[jira] Updated: (HADOOP-1935) NullPointerException in
internalReleaseCreate
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-1935:
-------------------------------------
Attachment: npePendingCreate3.patch
Fix findbugs warning introduced by earlier patch.
> 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: npePendingCreate3.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.
[jira] Updated: (HADOOP-1935) NullPointerException in
internalReleaseCreate
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-1935:
-------------------------------------
Priority: Blocker (was: Major)
> 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
> Priority: Blocker
> Fix For: 0.15.0
>
>
> 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.
[jira] Updated: (HADOOP-1935) NullPointerException in
internalReleaseCreate
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-1935:
-------------------------------------
Status: Open (was: Patch Available)
> 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: npePendingCreate2.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.
[jira] Issue Comment Edited: (HADOOP-1935) NullPointerException in
internalReleaseCreate
Posted by "Konstantin Shvachko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531122 ]
shv edited comment on HADOOP-1935 at 9/28/07 12:19 PM:
-----------------------------------------------------------------------
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}
You did not get rid of the NPE. Probably need to return.
was (Author: shv):
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.
[jira] Updated: (HADOOP-1935) NullPointerException in
internalReleaseCreate
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-1935:
-------------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
I just submitted this.
> 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: npePendingCreate3.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.
[jira] Updated: (HADOOP-1935) NullPointerException in
internalReleaseCreate
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-1935:
-------------------------------------
Attachment: npePendingCreate2.patch
Incorporates Konstantin's comments.
> 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: npePendingCreate2.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.