Hi Liu Le,
You're correct, that's an oversight that was designed but never
implemented. It's quite a rare circumstance but we should probably
implement the persistent promise as you suggested. Want to have a try at
making a patch for trunk?
-Todd
On Mon, Oct 28, 2013 at 1:57 AM, lei liu wrote:
In https://issues.apache.org/jira/browse/HDFS-1972 jira, there is one below
case:
Scenario 3: DN restarts during split brain period
(this scenario illustrates why I think we need to persistently record the
promise about who is active)
- block has 2 replicas, user asks to reduce to 1
- NN1 a
to HA branch. Thanks for the reviews
> HA: Datanode fencing mechanism
> --
>
> Key: HDFS-1972
> URL: https://issues.apache.org/jira/browse/HDFS-1972
> Project: Hadoop HDFS
>
HA: Datanode fencing mechanism
--
Key: HDFS-1972
URL: https://issues.apache.org/jira/browse/HDFS-1972
Project: Hadoop HDFS
Issue Type: Sub-task
Components: data-node, name-node
Reporter
