[HDDS-5881] Change S3G to OM RPC framework to keep persistent connection across multiple users

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Implemented
• Affects Version/s: 1.2.0
• Fix Version/s: 1.3.0
• Component/s: OM, S3
• Assignee: Ritesh Shukla
• Reporter: Ritesh Shukla
• Created: 21/Oct/21 20:34
• Updated: 06/May/22 21:02
• Resolved: 06/May/22 21:02

Description

Based on investigation in HDDS-5630 we find that the performance for S3G to OM can be improved by a large margin by keeping a single persistent connection between S3G and OM and reuse the connection across all users of S3 APIs. This needs the security model to change.

The tasks breakdown for this Jira lists the changes needed for this.

Issue Links

• relates to: HDDS-4440 Design Doc: Use per-request authentication and persistent connections between S3g and OM

Sub-Tasks

• Change proto definitions to include S3G authentication information: Resolved
• OM Validate S3 Auth for write requests: Resolved
• OM Auth Validate for read requests and handle non ratis enabled code.: Resolved
• Measure performance for the new changes.: Resolved
• Introduce new tests related to checks for new authentication method.: Resolved
• Authenticate with OM as S3G (Client side): Resolved
• Additional validations on client side: Resolved
• S3G and OM upgrade requirements.: Resolved
• Cleanup OmService injection: Resolved
• Make OM FailOverProxyProvider work across threads: Resolved
• Use s3Auth during proxy during decrypt in RpcClient: Resolved