[
https://issues.apache.org/jira/browse/HDDS-1262?focusedWorklogId=215794&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-215794
]
ASF GitHub Bot logged work on HDDS-1262:
----------------------------------------
Author: ASF GitHub Bot
Created on: 19/Mar/19 22:11
Start Date: 19/Mar/19 22:11
Worklog Time Spent: 10m
Work Description: hadoop-yetus commented on issue #625: HDDS-1262. In OM
HA OpenKey call Should happen only leader OM.
URL: https://github.com/apache/hadoop/pull/625#issuecomment-474604625
:broken_heart: **-1 overall**
| Vote | Subsystem | Runtime | Comment |
|:----:|----------:|--------:|:--------|
| 0 | reexec | 0 | Docker mode activated. |
| -1 | patch | 6 | https://github.com/apache/hadoop/pull/625 does not apply
to trunk. Rebase required? Wrong Branch? See
https://wiki.apache.org/hadoop/HowToContribute for help. |
| Subsystem | Report/Notes |
|----------:|:-------------|
| GITHUB PR | https://github.com/apache/hadoop/pull/625 |
| Console output |
https://builds.apache.org/job/hadoop-multibranch/job/PR-625/1/console |
| Powered by | Apache Yetus 0.9.0 http://yetus.apache.org |
This message was automatically generated.
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 215794)
Time Spent: 0.5h (was: 20m)
> 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
> Time Spent: 0.5h
> 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 message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
