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

James Thomas updated HDFS-6482:
-------------------------------

    Description: 
Right now blocks are placed into directories that are split into many 
subdirectories when capacity is reached. Instead we can use a block's ID to 
determine the path it should go in. This eliminates the need for the LDir data 
structure that facilitates the splitting of directories when they reach 
capacity as well as fields in ReplicaInfo that keep track of a replica's 
location.

An extension of the work in HDFS-3290.

  was:Right now blocks are placed into directories that are split into many 
subdirectories when capacity is reached. Instead we can use a block's ID to 
determine the path it should go in. This eliminates the need for the LDir data 
structure that facilitates the splitting of directories when they reach 
capacity as well as fields in ReplicaInfo that keep track of a replica's 
location.


> Use block ID-based block layout on datanodes
> --------------------------------------------
>
>                 Key: HDFS-6482
>                 URL: https://issues.apache.org/jira/browse/HDFS-6482
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: datanode
>    Affects Versions: 2.5.0
>            Reporter: James Thomas
>            Assignee: James Thomas
>         Attachments: HDFS-6482.patch
>
>
> Right now blocks are placed into directories that are split into many 
> subdirectories when capacity is reached. Instead we can use a block's ID to 
> determine the path it should go in. This eliminates the need for the LDir 
> data structure that facilitates the splitting of directories when they reach 
> capacity as well as fields in ReplicaInfo that keep track of a replica's 
> location.
> An extension of the work in HDFS-3290.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to