[
https://issues.apache.org/jira/browse/HDDS-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham updated HDDS-1347:
-------------------------------------
Description:
was:
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.
> In OM HA getS3Secret and createDelegationToken call Should happen only leader
> OM
> --------------------------------------------------------------------------------
>
> Key: HDDS-1347
> URL: https://issues.apache.org/jira/browse/HDDS-1347
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Bharat Viswanadham
> Assignee: Bharat Viswanadham
> Priority: Major
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
