[
https://issues.apache.org/jira/browse/HDFS-11096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089926#comment-16089926
]
Sean Mackrory commented on HDFS-11096:
--------------------------------------
Filed HDFS-12151 after looking into the logs deeper than I have in a while and
seeing that stuff is failing once you start rolling the DataNodes. In a
nutshell, Hadoop 2 clients can't write to Hadoop 3 DataNodes, so everything is
falling apart at that point. I've been making the mistake of assuming
all-processes-exit-0 => everything-is-working-great, but if jobs fails
completely the CLI still returns 0. I do believe I've checked for actual
success before, so I believe this did used to work and broke fairly recently,
but I'm going to dig deeper.
> Support rolling upgrade between 2.x and 3.x
> -------------------------------------------
>
> Key: HDFS-11096
> URL: https://issues.apache.org/jira/browse/HDFS-11096
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: rolling upgrades
> Affects Versions: 3.0.0-alpha1
> Reporter: Andrew Wang
> Assignee: Lei (Eddy) Xu
> Priority: Blocker
>
> trunk has a minimum software version of 3.0.0-alpha1. This means we can't
> rolling upgrade between branch-2 and trunk.
> This is a showstopper for large deployments. Unless there are very compelling
> reasons to break compatibility, let's restore the ability to rolling upgrade
> to 3.x releases.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
