[
https://issues.apache.org/jira/browse/HDDS-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham updated HDDS-1319:
-------------------------------------
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.
was:
In OM HA, currently, when openKey is called, in applyTransaction() on all OM
nodes, we make a call to SCM and write the allocateBlock information into OM DB
and also clientID will be generated by each OM node.
The proposed approach is:
1. In startTransaction, call openKey and the response returned should be used
to create a new OmRequest object and used in setting the transaction context.
And also modify the ozoneManager and KeymanagerImpl to handle the code with and
without ratis.
> In OM HA InitiateMultipartUpload call Should happen only leader OM
> ------------------------------------------------------------------
>
> Key: HDDS-1319
> URL: https://issues.apache.org/jira/browse/HDDS-1319
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Bharat Viswanadham
> Assignee: Bharat Viswanadham
> Priority: Major
>
> 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.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
