You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Ritesh H Shukla (Jira)" <ji...@apache.org> on 2021/10/18 23:09:00 UTC
[jira] [Reopened] (HDDS-5630) S3G keep connections to OM around
leading to slowness
[ https://issues.apache.org/jira/browse/HDDS-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ritesh H Shukla reopened HDDS-5630:
-----------------------------------
Reopening to tackle a targeted fix to address the authentication needs for secure S3G.
# Move the authentication logic to the application logic similar to HDDS-4440
# Have a single OM Client in S3G
# OM tackles per request authentication for secure S3G only.
> S3G keep connections to OM around leading to slowness
> -----------------------------------------------------
>
> Key: HDDS-5630
> URL: https://issues.apache.org/jira/browse/HDDS-5630
> Project: Apache Ozone
> Issue Type: Bug
> Components: S3
> Reporter: Ritesh H Shukla
> Assignee: Ritesh H Shukla
> Priority: Major
> Attachments: ClientCache20210902.patch
>
>
> S3G currently creates one Ozone Client per requests. The client uses Hadoop RPC to communicate with OM. The TCP connections with OM are not cleaned up post completion of the S3 requests which leads to large number of TCP connections to be open between S3G and OM. https://issues.apache.org/jira/browse/HDDS-4440 will eventually replace the use of Hadoop RPC but in the mean time it is prudent to look into how the current RPC usage can be improved.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org