[
https://issues.apache.org/jira/browse/HDFS-11207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Wang updated HDFS-11207:
-------------------------------
Fix Version/s: 3.0.0-alpha2
Release Note: HDFS-5079 was reverted since it introduced incompatible
protocol changes that blocked rolling upgrade.
Summary: Revert HDFS-5079. Cleaning up NNHAStatusHeartbeat.State
DatanodeProtocolProtos. (was: Unnecessary incompatible change of
NNHAStatusHeartbeat.state in DatanodeProtocolProtos)
I'm going to use this JIRA to log the revert for the 3.0.0-alpha2 release
notes. Thanks for taking care of this Kihwal and Eric!
> Revert HDFS-5079. Cleaning up NNHAStatusHeartbeat.State
> DatanodeProtocolProtos.
> -------------------------------------------------------------------------------
>
> Key: HDFS-11207
> URL: https://issues.apache.org/jira/browse/HDFS-11207
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: rolling upgrades
> Affects Versions: 3.0.0-alpha1
> Reporter: Eric Badger
> Assignee: Eric Badger
> Priority: Critical
> Fix For: 3.0.0-alpha2
>
> Attachments: HDFS-11207.001.patch
>
>
> HDFS-5079 changed the meaning of state in {{NNHAStatusHeartbeat}} when it
> added in the {{INITIALIZING}} state via {{HAServiceStateProto}}.
> Before change:
> {noformat}
> enum State {
> ACTIVE = 0;
> STANDBY = 1;
> }
> {noformat}
> After change:
> {noformat}
> enum HAServiceStateProto {
> INITIALIZING = 0;
> ACTIVE = 1;
> STANDBY = 2;
> }
> {noformat}
> So the new {{INITIALIZING}} state will be interpreted as {{ACTIVE}}, new
> {{ACTIVE}} interpreted as {{STANDBY}} and new {{STANDBY}} interpreted as
> unknown. Any rolling upgrade to 3.0.0 will break because the datanodes that
> haven't been updated will misinterpret the NN state.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
