[
https://issues.apache.org/jira/browse/HDFS-11096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Mackrory updated HDFS-11096:
---------------------------------
Attachment: HDFS-11096.005.patch
* Restored the old hadoop_actual_ssh. I did try a few cases of multi-token
commands through workers.sh and they didn't behave the same with my function if
you didn't quote the command or something. I'm trying to think of a better way
to differentiate between that function and my own that just takes quoted,
multi-line strings and therefore shouldn't be escaping the same way. They're
currently named hadoop_ssh_cmd (old one - expects a single command passed all
the way from workers.sh) and hadoop_ssh_cmds (new one - expects a quote script
passed directly from another script). But I'm not happy with that either.
* Fixed a bunch of issues when running as a non-root user. Some of these were
in the pull-over-http test, but one of them was actually in start-yarn.sh where
an arg is missing in a non-root branch of the script.
* Also fixed multi-cluster config in the pull-over-http.sh. They ended up using
the same YARN cluster ID when talking to the ZooKeeper cluster.
* Added license headers to several of the scripts, as the build started failing
without them.
I am now again blocked on what may be a bug in YARN or MR. The MapReduce
classpath seems all messed up in both tests. It wants me to specify
HADOOP_MAPRED_CLASSPATH in mapred-site.xml (even though the inferred value is
correct), and even then it can't find log4j.properties or yarn-site.xml.
> 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]
