[HDDS-1319] In OM HA InitiateMultipartUpload call Should happen only leader OM

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Done
• Component/s: OM HA, Ozone Manager
• Assignee: Bharat Viswanadham
• Reporter: Bharat Viswanadham
• Created: 21/Mar/19 16:42
• Updated: 04/Jun/20 20:16
• Resolved: 21/Mar/19 18:51

Description

In OM HA, currently, when initiate multipart upload is called, in applyTransaction() on all OM nodes, it generates a multipartUploadID. So, each OM generates a new multipartUploadID. But the response we give to the client is multipartUploadID generated from OM leader node.

 

Because this is the same multipartUploadID used during openKey and commitKey. (This will be sent from client who is creating this multipart upload for a key).

 

To solve this issue, we take similar approach of openKey, where multipartUploadID will be generated in startTransaction and the same should be sent to all OM's. So that during applyTransaction all OM's will have the same multipartUploadID.

 

Issue Links

• is a clone of: HDDS-1262 In OM HA OpenKey call Should happen only leader OM
• is cloned by: HDDS-1347 Implement GetS3Secret to use double buffer and cache.