You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Bharat Viswanadham (JIRA)" <ji...@apache.org> on 2019/03/21 18:52:00 UTC
[jira] [Resolved] (HDDS-1319) In OM HA InitiateMultipartUpload call
Should happen only leader OM
[ https://issues.apache.org/jira/browse/HDDS-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bharat Viswanadham resolved HDDS-1319.
--------------------------------------
Resolution: Done
> 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: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org