[
https://issues.apache.org/jira/browse/HDFS-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Shvachko updated HDFS-676:
-------------------------------------
Resolution: Fixed
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
I just committed this.
> NPE in FSDataset.updateReplicaUnderRecovery(..)
> -----------------------------------------------
>
> Key: HDFS-676
> URL: https://issues.apache.org/jira/browse/HDFS-676
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: data-node
> Affects Versions: 0.21.0
> Reporter: Tsz Wo (Nicholas), SZE
> Assignee: Konstantin Shvachko
> Fix For: 0.21.0
>
> Attachments: h676_20091005.patch, updateRUR.patch
>
>
> {noformat}
> java.io.IOException: java.lang.NullPointerException
> at
> org.apache.hadoop.hdfs.server.datanode.FSDataset.updateReplicaUnderRecovery(FSDataset.java:2089)
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.updateReplicaUnderRecovery(DataNode.java:1598)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:516)
> ...
> {noformat}
> The problem can be reproduced by calling updateReplicaUnderRecovery(blockid)
> with blockid not in the volumeMap.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
