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 16:43:00 UTC
[jira] [Created] (HDDS-1319) In OM HA InitiateMultipartUpload call
Should happen only leader OM
Bharat Viswanadham created HDDS-1319:
----------------------------------------
Summary: 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
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.
--
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