[
https://issues.apache.org/jira/browse/HDFS-11643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Wang updated HDFS-11643:
-------------------------------
Priority: Blocker (was: Critical)
Bumping to blocker for visibility. Looks like the patch needs a rebase, also
looks like a stray dev comment:
{noformat}
// Preconditions.checkState(callId.get() == null);
{noformat}
Recommend we reword this as "with a few additions. First, the addition of
favoredNodes that is a". Could also add some "<p>" tags for linebreaks.
{noformat}
* Progressable, ChecksumOpt)} with first addition of favoredNodes that is a
{noformat}
Let's throw a Precondition exception when a user sets both {{asReplicatedFile}}
and also {{ecPolicyName}}, since these are exclusive options. Would be good to
unit test this too.
Otherwise looks pretty good! Thanks Sammi.
> 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
>
>
> 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]
