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-5121) add RPCs for creating and manipulating cache pools
Date Fri, 23 Aug 2013 22:05:52 GMT

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

Colin Patrick McCabe updated HDFS-5121:

    Attachment: HDFS-5121-caching.001.patch

* add and implement RPCs for creating/modifying and deleting pools.

* add CachePoolInfo, which is a client-side representation of pool state.  CachePool is the
server-side representation of this state, and will eventually have more fields that aren't
important to the client.  Also, CachePool cannot contain null fields.

* add the retry cache glue code needed for the earlier path directive RPCs, as well as for
these new RPCs.  This is only required for the AtMostOnce RPCs-- idempotent ones are unaffected.

* enforce pool permissions (i.e., user+group+mode) when adding or removing path cache directives.
 (In contrast, creating, modifying or deleting pools can only be done by the superuser).

* fix unit test failure in TestPathCacheRequests -- inverted conditional in DFSUtil.isPathValid.

* I noticed that the {{RemoteIterators}} I was creating in the patch looked a lot like the
ones I had created earlier, so I pushed the common code into {{BatchedRemoteIterator}}.
> add RPCs for creating and manipulating cache pools
> --------------------------------------------------
>                 Key: HDFS-5121
>                 URL: https://issues.apache.org/jira/browse/HDFS-5121
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: datanode, namenode
>    Affects Versions: HDFS-4949
>            Reporter: Colin Patrick McCabe
>            Assignee: Colin Patrick McCabe
>         Attachments: HDFS-5121-caching.001.patch
> We should add RPCs for creating and manipulating cache pools.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message