[
https://issues.apache.org/jira/browse/HDFS-11873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16022232#comment-16022232
]
Weiwei Yang commented on HDFS-11873:
------------------------------------
Attached a test case to reproduce this issue. There are two tests in the class
# {{testReuseHttpConnection}} creates a http client and uses this client to
submit 2 create volume requests, on current code base, 1st request succeed and
*2nd request is stuck* (eventually times out).
# {{testNewConnectionPerRequest}} instead creating a new http client to submit
2 create volume requests, on current code base, they all succeed.
[~xyao] and [~anu], please take a look at this JIRA and the test case I
attached. I am not familiar with the netty stuff but based on my investigation,
I think the problem is on the server side. Please take a look and let me know
if I miss anything.
Thank you.
> Ozone: Object store handler cannot serve requests from same http client
> -----------------------------------------------------------------------
>
> Key: HDFS-11873
> URL: https://issues.apache.org/jira/browse/HDFS-11873
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: HDFS-7240
> Reporter: Weiwei Yang
> Assignee: Weiwei Yang
> Priority: Critical
> Attachments: HDFS-11873-HDFS-7240.testcase.patch
>
>
> This issue was found when I worked on HDFS-11846. Instead of creating a new
> http client instance per request, I tried to reuse {{CloseableHttpClient}} in
> {{OzoneClient}} class in a {{PoolingHttpClientConnectionManager}}. However,
> every second request from the http client hangs, which could not get
> dispatched to {{ObjectStoreJerseyContainer}}. There seems to be something
> wrong in the netty pipeline, this jira aims to 1) fix the problem in the
> server side 2) use the pool for client http clients to reduce the resource
> overhead.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
