[
https://issues.apache.org/jira/browse/HDDS-1262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham updated HDDS-1262:
-------------------------------------
Description:
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.
was:
In OM HA, currently when allocateBlock is called, in applyTransaction() on all
OM nodes, we make a call to SCM and write the allocateBlock information into OM
DB. The problem with this is, every OM allocateBlock and appends new BlockInfo
into OMKeyInfom and also this a correctness issue. (As all OM's should have the
same block information for a key, even though eventually this might be changed
during key commit)
The proposed approach is:
1. Calling SCM for allocation of block will happen outside of ratis, and this
block information is passed and writing to DB will happen via Ratis.
> In OM HA OpenKey call Should happen only leader OM
> --------------------------------------------------
>
> Key: HDDS-1262
> URL: https://issues.apache.org/jira/browse/HDDS-1262
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Bharat Viswanadham
> Assignee: Bharat Viswanadham
> Priority: Major
> Labels: pull-request-available
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
