[
https://issues.apache.org/jira/browse/HDDS-1499?focusedWorklogId=239332&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-239332
]
ASF GitHub Bot logged work on HDDS-1499:
----------------------------------------
Author: ASF GitHub Bot
Created on: 08/May/19 17:30
Start Date: 08/May/19 17:30
Worklog Time Spent: 10m
Work Description: anuengineer commented on pull request #798: HDDS-1499.
OzoneManager Cache.
URL: https://github.com/apache/hadoop/pull/798#discussion_r282164867
##########
File path:
hadoop-hdds/common/src/main/java/org/apache/hadoop/utils/db/Table.java
##########
@@ -97,6 +102,28 @@ void putWithBatch(BatchOperation batch, KEY key, VALUE
value)
*/
String getName() throws IOException;
+ /**
+ * Add entry to the table cache.
+ *
+ * If the cacheKey already exists, it will override the entry.
+ * @param cacheKey
+ * @param cacheValue
+ */
Review comment:
well, I was really hoping that the fact that there is a cache is not visible
to the layer that is reading and writing.
Is there a reason why that should be exposed to calling applications?
----------------------------------------------------------------
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: 239332)
Time Spent: 1h 20m (was: 1h 10m)
> OzoneManager Cache
> ------------------
>
> Key: HDDS-1499
> URL: https://issues.apache.org/jira/browse/HDDS-1499
> 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 20m
> Remaining Estimate: 0h
>
> In this Jira, we shall implement a cache for Table.
> As with OM HA, we are planning to implement double buffer implementation to
> flush transaction in a batch, instead of using rocksdb put() for every
> operation. When this comes in to place we need cache in OzoneManager HA to
> handle/server the requests for validation/returning responses.
>
> This Jira will implement Cache as an integral part of the table. In this way
> users using this table does not need to handle like check cache/db. For this,
> we can update get API in the table to handle the cache.
>
> This Jira will implement:
> # Cache as a part of each Table.
> # Uses this cache in get().
> # Exposes api for cleanup, add entries to cache.
> Usage to add the entries in to cache will be done in further jira's.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
