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-1262) In OM HA OpenKey call Should happen only leader OM
Date Wed, 27 Mar 2019 00:08:00 GMT

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

ASF GitHub Bot logged work on HDDS-1262:

                Author: ASF GitHub Bot
            Created on: 27/Mar/19 00:07
            Start Date: 27/Mar/19 00:07
    Worklog Time Spent: 10m 
      Work Description: bharatviswa504 commented on issue #626: HDDS-1262. In OM HA OpenKey
and initiateMultipartUpload call Should happen only leader OM.
URL: https://github.com/apache/hadoop/pull/626#issuecomment-476904363
   Not sure why for this PR yetus is throwing mvn install errors.
   I am able to compile locally on my dev machine.
   Posted a patch to the 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: 219014)
    Time Spent: 4h 40m  (was: 4.5h)

> In OM HA OpenKey call Should happen only leader OM
> --------------------------------------------------
>                 Key: HDDS-1262
>                 URL: https://issues.apache.org/jira/browse/HDDS-1262
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>            Reporter: Bharat Viswanadham
>            Assignee: Bharat Viswanadham
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: HDDS-1262.01.patch
>          Time Spent: 4h 40m
>  Remaining Estimate: 0h
> 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. 

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