[
https://issues.apache.org/jira/browse/HDFS-11096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16200410#comment-16200410
]
Allen Wittenauer commented on HDFS-11096:
-----------------------------------------
bq. if you didn't quote the command
Yup. This is all fallout from a decision made way back in 0.1 that's extremely
hard to fix: HADOOP_OPTS is space delimited and anything that even comes close
to touching it is expecting that behavior. It's easy to blame Doug for it, but
it's not really his fault given he copied the original code from (he thinks)
Tomcat. Besides, a lot of inexperienced shell programmers make the same mistake
and it still shows up in new code despite this being a known gotcha (see:
almost every project even remotely related to Hadoop, e.g., RATIS-29).
The bigger problem is that it's super hard to fix once you realize just how
screwed up everything is: HADOOP-13365, HBASE-17285, ...
[Worthwhile noting that while HADOOP-13365 fixes a large chunk of the problem
it still doesn't fix everything, e.g., the workers subsystem.]
> 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: Sean Mackrory
> Priority: Blocker
> Attachments: HDFS-11096.001.patch, HDFS-11096.002.patch,
> HDFS-11096.003.patch, HDFS-11096.004.patch, HDFS-11096.005.patch
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
