[
https://issues.apache.org/jira/browse/HDDS-5614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401429#comment-17401429
]
Ritesh H Shukla commented on HDDS-5614:
---------------------------------------
[~adoroszlai] here are the steps
# Generate load from multiple clients/threads to one s3g (I have tested with
just a single client and around 10 threads)
# Use lsof -p to track the number of open connections for the s3g process.
I see thousands of open connections between S3G and OM during the steps above.
The same is not true the HTTP endpoint used by the client or the connection
between S3G and Datanode.
Eventually with enough load, the connections are waiting to get a socket.
> The OzoneClient in s3 endpoint is not closed correctly
> ------------------------------------------------------
>
> Key: HDDS-5614
> URL: https://issues.apache.org/jira/browse/HDDS-5614
> Project: Apache Ozone
> Issue Type: Bug
> Components: S3
> Reporter: Tsz-wo Sze
> Assignee: Tsz-wo Sze
> Priority: Major
>
> In [~kerneltime]'s S3 tests, we found that the close() method in
> EndpointBase.client, which is an OzoneClient, is never called.
> In OzoneClientProducer, client.close() is called in the destroy() method.
> However, the createClient() method keeps overwriting the "client" field. Only
> the last client will be closed.
> {code:java}
> //OzoneClientProducer.java
> @Produces
> public OzoneClient createClient() throws WebApplicationException,
> IOException {
> client = getClient(ozoneConfiguration);
> return client;
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
