[
https://issues.apache.org/jira/browse/HDFS-12461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167273#comment-16167273
]
Anu Engineer commented on HDFS-12461:
-------------------------------------
Sorry, I found out why I thought this mapping was wrong. This is not a bug.
This happens only on the SCM node. All the container files show up in the
*repository* directory. But if you have a chance, verify that data is placed on
all disks and resolve this issue.
> Ozone: Ozone data placement is not even
> ---------------------------------------
>
> Key: HDFS-12461
> URL: https://issues.apache.org/jira/browse/HDFS-12461
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
> Affects Versions: HDFS-7240
> Reporter: Anu Engineer
> Priority: Blocker
> Labels: ozoneMerge
>
> On a machine with 3 data disks, Ozone keeps on picking the same disk to place
> all containers. Looks like we have a bug in the round robin selection of
> disks.
> Steps to Reproduce:
> 1. Install an Ozone cluster.
> 2. Make sure that datanodes have more than one disk.
> 3. Run corona few times, each run creates more containers.
> 4. Login into the data node.
> 5. Run a command like tree or ls -R /data or independently verify each
> location.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
