[HDDS-5630] S3G keep connections to OM around leading to slowness

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: S3
• Assignee: Neil Joshi
• Reporter: Ritesh Shukla
• Created: 17/Aug/21 21:34
• Updated: 17/Mar/23 03:36
• Resolved: 17/Mar/23 03:36

Description

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.

Issue Links

• duplicates: HDDS-4440 Design Doc: Use per-request authentication and persistent connections between S3g and OM
• is related to: HDDS-5614 The OzoneClient in s3 endpoint is not closed correctly
• relates to: HDDS-4440 Design Doc: Use per-request authentication and persistent connections between S3g and OM