You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Mike Percy (JIRA)" <ji...@apache.org> on 2017/04/24 23:12:04 UTC

[jira] [Updated] (KUDU-1980) Change BlockCache from a static singleton to one per BlockManager

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

Mike Percy updated KUDU-1980:
-----------------------------
    Issue Type: Improvement  (was: Bug)

> Change BlockCache from a static singleton to one per BlockManager
> -----------------------------------------------------------------
>
>                 Key: KUDU-1980
>                 URL: https://issues.apache.org/jira/browse/KUDU-1980
>             Project: Kudu
>          Issue Type: Improvement
>          Components: fs
>    Affects Versions: 1.3.1
>            Reporter: Mike Percy
>
> It would be useful to change BlockCache from being a static singleton to being instantiated and owned by a single FsManager or BlockManager. Right now we have a "hack" in LogBlockManager to randomize starting block IDs when we are running under GTest to avoid cache incoherency in between test runs. This causes differences in block id naming between the test environment and production, making it hard to catch certain types of problems.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)