hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-5651) remove dfs.namenode.caching.enabled and fix HA state transition race
Date Tue, 31 Dec 2013 20:50:51 GMT

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

Colin Patrick McCabe updated HDFS-5651:
---------------------------------------

    Attachment: HDFS-5651.008.patch

> remove dfs.namenode.caching.enabled and fix HA state transition race
> --------------------------------------------------------------------
>
>                 Key: HDFS-5651
>                 URL: https://issues.apache.org/jira/browse/HDFS-5651
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>    Affects Versions: 3.0.0
>            Reporter: Colin Patrick McCabe
>            Assignee: Colin Patrick McCabe
>         Attachments: HDFS-5651.001.patch, HDFS-5651.002.patch, HDFS-5651.003.patch, HDFS-5651.004.patch,
HDFS-5651.006.patch, HDFS-5651.006.patch, HDFS-5651.008.patch
>
>
> We can remove dfs.namenode.caching.enabled and simply always enable caching, similar
to how we do with snapshots and other features.  The main overhead is the size of the cachedBlocks
GSet.  However, we can simply make the size of this GSet configurable, and people who don't
want caching can set it to a very small value.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message