[ https://issues.apache.org/jira/browse/HDFS-11643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15966691#comment-15966691 ]
Andrew Wang commented on HDFS-11643: ------------------------------------ Agree, at least for the balancer, I think for now we only need a new boolean parameter like you say. This also relates to HDFS-11644. If DFSStripedOutputStream no longer implements Syncable, then the Balancer's FSDataOutputStream#hflush will fallback to just doing a flush. For the balancer, I think we'd still prefer writing a replicated file and doing a real hflush, since otherwise {{write2IdFile}} won't function correctly. > 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 > Priority: Critical > Labels: hdfs-ec-3.0-must-do > > 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: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org