[jira] [Updated] (KUDU-563) Make LogCache more flexible with regard to what it keeps in memory

["Mike Percy (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KUDU-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Percy updated KUDU-563:
----------------------------
    Parent: KUDU-560

> Make LogCache more flexible with regard to what it keeps in memory
> ------------------------------------------------------------------
>
>                 Key: KUDU-563
>                 URL: https://issues.apache.org/jira/browse/KUDU-563
>             Project: Kudu
>          Issue Type: Sub-task
>          Components: consensus
>    Affects Versions: M4.5
>            Reporter: David Alves
>            Assignee: Todd Lipcon
>
> Right now LogCache keeps everything in memory that anyone might need. This is legacy behavior from when we couldn't fill the cache from disk and we don't need it anymore.
> A couple alternatives could work, while making the cache more flexible. Here's one:
> - Make the pin a suggestion, i.e. under memory pressure we could still evict past the pin, but otherwise we don't.
> - Make the pin move with the majority replicated index or even with the committed index, that way the ops that most people are likely to need are in memory but others aren't/
> - Make the cache not cache anything behind the pin



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)