[HDDS-6220] EC: Introduce a gRPC client implementation for EC with really async WriteChunk and PutBlock

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: EC-Branch
• Component/s: EC
• Labels: pull-request-available
• Target Version/s: EC-Branch
• Assignee: István Fajth
• Reporter: István Fajth
• Created: 24/Jan/22 13:29
• Updated: 25/Jan/22 17:15
• Resolved: 25/Jan/22 16:55

Description

As we do still support the writes via the gRPC client with the use of STAND_ALONE replication type in our code, we should not touch the current class, in order to achieve really async WriteChunk and PutBlock calls.
All other calls are synchronized, so this is just the two main concern, as these affects the EC write path.
In order to have these calls as really async calls, we need to have an altered client implementation, that does not synchronize these calls, and use that for EC writes as we can not safely and easily change the semantics of the original client for the STAND_ALONE replication type.

Issue Links

• is a child of: HDDS-5954 EC: Review the TODOs in GRPC Xceiver client and fix them.
• links to: GitHub Pull Request #3016