hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sam rash (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (HDFS-1214) hdfs client metadata cache
Date Tue, 22 Jun 2010 22:09:52 GMT

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

sam rash reassigned HDFS-1214:

    Assignee: sam rash

> hdfs client metadata cache
> --------------------------
>                 Key: HDFS-1214
>                 URL: https://issues.apache.org/jira/browse/HDFS-1214
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>          Components: hdfs client
>            Reporter: Joydeep Sen Sarma
>            Assignee: sam rash
> In some applications, latency is affected by the cost of making rpc calls to namenode
to fetch metadata. the most obvious case are calls to fetch file/directory status. applications
like hive like to make optimizations based on file size/number etc. - and for such optimizations
- 'recent' status data (as opposed to most up-to-date) is acceptable. in such cases, a cache
on the DFS client that transparently caches metadata would be greatly benefit applications.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message