[HDDS-1262] In OM HA OpenKey call Should happen only leader OM

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.4.1
• Component/s: OM HA, Ozone Manager
• Labels: pull-request-available
• Target Version/s: 0.5.0
• Assignee: Bharat Viswanadham
• Reporter: Bharat Viswanadham
• Created: 13/Mar/19 21:39
• Updated: 04/Jun/20 20:17
• Resolved: 27/Mar/19 04:48

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.

 

This Jira also implements HDDS-1319. 

Issue Links

• is a clone of: HDDS-1250 In OM HA AllocateBlock call where connecting to SCM from OM should not happen on Ratis
• is cloned by: HDDS-1319 In OM HA InitiateMultipartUpload call Should happen only leader OM
• links to: GitHub Pull Request #626