Yicong Cai created HDFS-14429:
---------------------------------
Summary: Block remain in COMMITTED but not COMPLETE cause by
Decommission
Key: HDFS-14429
URL: https://issues.apache.org/jira/browse/HDFS-14429
Project: Hadoop HDFS
Issue Type: Bug
Affects Versions: 2.9.2
Reporter: Yicong Cai
In the following scenario, the Block will remain in the COMMITTED but not
COMPLETE state and cannot be closed properly:
# Client writes Block(bk1) to three data nodes (dn1/dn2/dn3).
# bk1 has been completely written to three data nodes, and the data node
succeeds FinalizeBlock, joins IBR and waits to report to NameNode.
# The client commits bk1 after receiving the ACK.
# When the DN has not been reported to the IBR, all three nodes dn1/dn2/dn3
enter Decommissioning.
# The DN reports the IBR, but the block cannot be completed normally.
Then it will lead to the following related exceptions:
{panel:title=Exception}
2019-04-02 13:40:31,882 INFO namenode.FSNamesystem
(FSNamesystem.java:checkBlocksComplete(2790)) - BLOCK*
blk_4313483521_3245321090 is COMMITTED but not COMPLETE(numNodes= 3 >= minimum
= 1) in file xxx
2019-04-02 13:40:31,882 INFO ipc.Server (Server.java:logException(2650)) - IPC
Server handler 499 on 8020, call Call#122552 Retry#0
org.apache.hadoop.hdfs.protocol.ClientProtocol.addBlock from xxx:47615
org.apache.hadoop.hdfs.server.namenode.NotReplicatedYetException: Not
replicated yet: xxx
at
org.apache.hadoop.hdfs.server.namenode.FSDirWriteFileOp.validateAddBlock(FSDirWriteFileOp.java:171)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getAdditionalBlock(FSNamesystem.java:2579)
at
org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.addBlock(NameNodeRpcServer.java:846)
at
org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.addBlock(ClientNamenodeProtocolServerSideTranslatorPB.java:510)
at
org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:503)
at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:989)
at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:871)
at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:817)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1893)
at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2606)
{panel}
And will cause the scenario described in HDFS-12747
The root cause is that addStoredBlock does not consider the case where the
replications are in Decommission.
This problem needs to be fixed like HDFS-11499.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
