hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bharat Viswanadham (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDDS-1250) In OM HA AllocateBlock call where connecting to SCM from OM should not happen on Ratis
Date Fri, 15 Mar 2019 00:02:00 GMT

     [ https://issues.apache.org/jira/browse/HDDS-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Bharat Viswanadham updated HDDS-1250:
-------------------------------------
    Target Version/s: 0.5.0

> In OM HA AllocateBlock call where connecting to SCM from OM should not happen on Ratis
> --------------------------------------------------------------------------------------
>
>                 Key: HDDS-1250
>                 URL: https://issues.apache.org/jira/browse/HDDS-1250
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>            Reporter: Bharat Viswanadham
>            Assignee: Bharat Viswanadham
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message