[ 
https://issues.apache.org/jira/browse/HDDS-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16793940#comment-16793940
 ] 

Hadoop QA commented on HDDS-1250:
---------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  7s{color} 
| {color:red} https://github.com/apache/hadoop/pull/591 does not apply to 
trunk. Rebase required? Wrong Branch? See 
https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| GITHUB PR | https://github.com/apache/hadoop/pull/591 |
| JIRA Issue | HDDS-1250 |
| Console output | 
https://builds.apache.org/job/hadoop-multibranch/job/PR-591/10/console |
| Powered by | Apache Yetus 0.9.0 http://yetus.apache.org |


This message was automatically generated.



> 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: 2h 20m
>  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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to