You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "xupeng (JIRA)" <ji...@apache.org> on 2016/04/26 09:15:13 UTC

[jira] [Commented] (HDFS-10328) Add cache pool level replication managment

    [ https://issues.apache.org/jira/browse/HDFS-10328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15257676#comment-15257676 ] 

xupeng commented on HDFS-10328:
-------------------------------

Attach a patch. 

User can set replication for pool by using "cacheadmin -addPool -replication" or "cacheadmin -modifyPool -replication". When adding a cache directive into pool without setting replication num, the cache directive will inherit replication configuration from cache pool. 

Also you can override this setting by using “cacheadmin -addDirective  -replication” or "cacheadmin -modifyDirective -replication". 



> Add cache pool level replication managment 
> -------------------------------------------
>
>                 Key: HDFS-10328
>                 URL: https://issues.apache.org/jira/browse/HDFS-10328
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: caching
>            Reporter: xupeng
>            Assignee: xupeng
>            Priority: Minor
>             Fix For: 2.3.0
>
>         Attachments: HADOOP-10328.001.patch
>
>
> For now, hdfs cacheadmin can not set a replication num for cachepool. Each cache directive added in the cache pool should set their own replication num individually. 
> Consider this situation, we add daily hive table into cache pool "hive" .Each time i should set the same replication num for every table directive in the same cache pool.  
> I think we should enable setting a replication num for cachepool that every cache directive in the pool can inherit replication configuration from the pool. Also cache directive can override replication configuration explicitly by calling "add & modify  directive -replication" command from cli.    



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