[
https://issues.apache.org/jira/browse/HDFS-11643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15994367#comment-15994367
]
SammiChen edited comment on HDFS-11643 at 5/3/17 6:58 AM:
----------------------------------------------------------
I add check that ID lock file should be a replicate file and manually tested
"fail before, works after" behavior since such an auto unit test is not
feasible given the lock file is enforced to be a replicate file.
was (Author: sammi):
Add check that ID lock file should be a replicate file
> Balancer fencing fails when writing erasure coded lock file
> -----------------------------------------------------------
>
> Key: HDFS-11643
> URL: https://issues.apache.org/jira/browse/HDFS-11643
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: balancer & mover, erasure-coding
> Affects Versions: 3.0.0-alpha1
> Reporter: Andrew Wang
> Assignee: SammiChen
> Priority: Blocker
> Labels: hdfs-ec-3.0-must-do
> Attachments: HDFS-11643.001.patch, HDFS-11643.002.patch,
> HDFS-11643.003.patch, HDFS-11643.004.patch, HDFS-11643.005.patch,
> HDFS-11643.006.patch, HDFS-11643.007.patch, HDFS-11643.008.patch
>
>
> At startup, the balancer writes its hostname to the lock file and calls
> hflush(). hflush is not supported for EC files, so this fails when the entire
> filesystem is erasure coded.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
