hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Work logged] (HDDS-1250) In OM HA AllocateBlock call where connecting to SCM from OM should not happen on Ratis
Date Mon, 18 Mar 2019 18:22:00 GMT

     [ https://issues.apache.org/jira/browse/HDDS-1250?focusedWorklogId=214931&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-214931

ASF GitHub Bot logged work on HDDS-1250:

                Author: ASF GitHub Bot
            Created on: 18/Mar/19 18:21
            Start Date: 18/Mar/19 18:21
    Worklog Time Spent: 10m 
      Work Description: bharatviswa504 commented on issue #591: HDDS-1250: IIn OM HA AllocateBlock
call where connecting to SCM from OM should not happen on Ratis.
URL: https://github.com/apache/hadoop/pull/591#issuecomment-474041921
   Test failure's failing are failing due to 
   300000 is not within min = 500 or max = 100000
   This will be taken care in the below jira.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

Issue Time Tracking

    Worklog Id:     (was: 214931)
    Time Spent: 3h 40m  (was: 3.5h)

> 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: 3h 40m
>  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

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

View raw message