[HDFS-15078] RBF: Should check connection channel before sending RPC to namenode

• Type: Improvement
• Status: Patch Available
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.3.0
• Component/s: rbf
• Assignee: Hui Fei
• Reporter: Hui Fei
• Created: 23/Dec/19 15:20
• Updated: 17/Dec/21 03:28

Description

dfsrouter logs show that

2019-12-20 04:11:26,724 WARN org.apache.hadoop.ipc.Server: IPC Server handler 6400 on 8888, call org.apache.hadoop.hdfs.protocol.ClientProtocol.create from 10.83.164.11:56908 Call#2 Retry#0: output error
2019-12-20 04:11:26,724 INFO org.apache.hadoop.ipc.Server: IPC Server handler 125 on 8888 caught an exception
java.nio.channels.ClosedChannelException
at sun.nio.ch.SocketChannelImpl.ensureWriteOpen(SocketChannelImpl.java:270)
at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:461)
at org.apache.hadoop.ipc.Server.channelWrite(Server.java:2731)
at org.apache.hadoop.ipc.Server.access$2100(Server.java:134)
at org.apache.hadoop.ipc.Server$Responder.processResponse(Server.java:1089)
at org.apache.hadoop.ipc.Server$Responder.doRespond(Server.java:1161)
at org.apache.hadoop.ipc.Server$Connection.sendResponse(Server.java:2109)
at org.apache.hadoop.ipc.Server$Connection.access$400(Server.java:1229)
at org.apache.hadoop.ipc.Server$Call.sendResponse(Server.java:631)
at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2245)

Maybe checking connection between client and router is better before sendingrpc to namenode

Issue Links

• is related to: HDFS-15079 RBF: Client maybe get an unexpected result with network anomaly
• relates to: HDFS-15310 RBF: Not proxy client's clientId and callId caused RetryCache invalid in NameNode.
• relates to: HDFS-16388 The namenode should check the connection channel before the RPC returns data