You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Kihwal Lee (JIRA)" <ji...@apache.org> on 2016/12/08 21:51:00 UTC

[jira] [Resolved] (HDFS-11207) Unnecessary incompatible change of NNHAStatusHeartbeat.state in DatanodeProtocolProtos

     [ https://issues.apache.org/jira/browse/HDFS-11207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kihwal Lee resolved HDFS-11207.
-------------------------------
    Resolution: Done

> Unnecessary incompatible change of NNHAStatusHeartbeat.state in 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
>         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-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org