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

ASF GitHub Bot logged work on HDDS-1638:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 13/Jun/19 21:21
            Start Date: 13/Jun/19 21:21
    Worklog Time Spent: 10m 
      Work Description: bharatviswa504 commented on issue #956: HDDS-1638.  
Implement Key Write Requests to use Cache and DoubleBuffer.
URL: https://github.com/apache/hadoop/pull/956#issuecomment-501883650
 
 
   Added tests for the classes.
 
----------------------------------------------------------------
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: 259920)
    Time Spent: 1h  (was: 50m)

> Implement Key Write Requests to use Cache and DoubleBuffer
> ----------------------------------------------------------
>
>                 Key: HDDS-1638
>                 URL: https://issues.apache.org/jira/browse/HDDS-1638
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>          Components: Ozone Manager
>            Reporter: Bharat Viswanadham
>            Assignee: Bharat Viswanadham
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> Implement Key write requests to use OM Cache, double buffer. 
> In this Jira will add the changes to implement key operations, and HA/Non-HA 
> will have a different code path, but once all requests are implemented will 
> have a single code path.



--
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