[HDDS-1250] In OM HA AllocateBlock call where connecting to SCM from OM should not happen on Ratis

• 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: 11/Mar/19 22:23
• Updated: 04/Jun/20 20:16
• Resolved: 18/Mar/19 20:53

Description

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.

Issue Links

• is cloned by: HDDS-1262 In OM HA OpenKey call Should happen only leader OM
• links to: GitHub Pull Request #591