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

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

                Author: ASF GitHub Bot
            Created on: 17/Jul/19 16:00
            Start Date: 17/Jul/19 16:00
    Worklog Time Spent: 10m 
      Work Description: bharatviswa504 commented on issue #1100: HDDS-1802. Add 
Eviction policy for table cache.
URL: https://github.com/apache/hadoop/pull/1100#issuecomment-512343961
 
 
   @arp7 Thanks for the review.
   I have addressed the review comments.
 
----------------------------------------------------------------
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: 278286)
    Time Spent: 3h  (was: 2h 50m)

> Add Eviction policy for table cache
> -----------------------------------
>
>                 Key: HDDS-1802
>                 URL: https://issues.apache.org/jira/browse/HDDS-1802
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>            Reporter: Bharat Viswanadham
>            Assignee: Bharat Viswanadham
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 3h
>  Remaining Estimate: 0h
>
> In this Jira we will add eviction policy for table cache.
> In this Jira, we will add 2 eviction policies for the cache.
> NEVER, // Cache will not be cleaned up. This mean's the table maintains full 
> cache.
> AFTERFLUSH // Cache will be cleaned up, once after flushing to DB.
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to