[
https://issues.apache.org/jira/browse/HDFS-12890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shashikant Banerjee updated HDFS-12890:
---------------------------------------
Attachment: HDFS-12890-HDFS-7240.004.patch
Thanks [~msingh] , for the review comments.
As per our discussion, in case, the exception is caught at netty client side,
the code now handles it , by removing all the pending future responses from the
response map and marking them completeExceptionally.
The same Exception is caught at XceiverClient where the exception is being
unwrapped in case its an IOException as being done in
RequestHedgingProxyProvider and propagated through to the client. I tried a
test by harcoding the Exception in ChannelRead0 function in XceiverClientHandler
and running putKey test in testOzoneRpcClient and it works.
> Ozone: XceiverClient should have upper bound on async requests
> --------------------------------------------------------------
>
> Key: HDFS-12890
> URL: https://issues.apache.org/jira/browse/HDFS-12890
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: HDFS-7240
> Affects Versions: HDFS-7240
> Reporter: Shashikant Banerjee
> Assignee: Shashikant Banerjee
> Fix For: HDFS-7240
>
> Attachments: HDFS-12890-HDFS-7240.001.patch,
> HDFS-12890-HDFS-7240.002.patch, HDFS-12890-HDFS-7240.003.patch,
> HDFS-12890-HDFS-7240.004.patch
>
>
> XceiverClient-ratis maintains upper bound on the no of outstanding async
> requests . XceiverClient
> should also impose an upper bound on the no of outstanding async requests
> received from client
> for write.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
