Jonathan,
I actually did all my testing on RC1. Sorry for the confusion. I'll respond on
the RC1 thread.
-Eric
On Monday, October 28, 2019, 8:00:20 PM CDT, Jonathan Hung
wrote:
Thanks Eric! I sent out an RC1 earlier last week, not sure if you saw that. The
only diff between RC1 and RC0
Thanks Eric! I sent out an RC1 earlier last week, not sure if you saw that.
The only diff between RC1 and RC0 is HDFS-14667. If RC1 looks good to you
then it'd be great to get your testing results on that thread.
Jonathan Hung
On Mon, Oct 28, 2019 at 1:06 PM epa...@apache.org wrote:
>
Compatibility testing has gone well for me.
- In a 4-node cluster, I ran YARN rolling upgrade tests between 2.8.5 and 2.10.0
- In a 4-node cluster, I ran YARN rolling upgrade tests between 2.10.0 and trunk
- With one 4-node cluster running 2.10.0 and one 4-node cluster running trunk,
I ran a
Ah! Yes! That makes sense. I will use the mapredonhdfs framework in my next
set of tests.
The other compatibility tests that I ran worked as expected.
-Eric
On Saturday, October 26, 2019, 12:29:54 PM CDT, Jonathan Hung
wrote:
Hi Eric, I took a quick look, are you using
Hi Eric, I took a quick look, are you using
mapreduce.application.framework.path to run your MR jobs? If not, this
seems like expected behavior if AM and tasks get launched on different NMs
with different locally installed hadoop versions?
Jonathan Hung
On Sat, Oct 26, 2019 at 8:55 AM
I ran a few compatibility tests between 2.10.0 and 3.3.0 (trunk)
Unfortunately, I ran into the following problem:
Running with 2.10 RM and 3.3.0 (trunk) NM fails attempts with the following
error:
2019-10-26 15:44:06,885 WARN [main] org.apache.hadoop.mapred.YarnChild:
Exception running child
Hi Eric, we've run some basic HDFS commands with a 3.2.1 namenode and
2.10.0 clients and datanodes. Everything worked as expected.
Jonathan Hung
On Tue, Oct 22, 2019 at 3:04 PM Eric Badger
wrote:
> Hi Jonathan,
>
> Thanks for putting this RC together. You stated that there are
> improvements
Hi Jonathan,
Thanks for putting this RC together. You stated that there are improvements
related to rolling upgrades from 2.x to 3.x and I know I have seen multiple
JIRAs getting committed to that effect. Could you describe any tests that
you have done to verify rolling upgrade compatibility for
Thanks Konstantin and Zhankun. Unfortunately a feature slipped our radar
(HDFS-14667). Since this is the first of a minor release, we would like to
get it into 2.10.0.
HDFS-14667 has been committed to branch-2.10.0, I will be rolling an RC1
shortly.
Jonathan Hung
On Tue, Oct 22, 2019 at 1:39
Thanks for the effort, Jonathan!
+1 (non-binding) on RC0.
- Set up a single node cluster with the binary tarball
- Run Spark Pi and pySpark job
BR,
Zhankun
On Tue, 22 Oct 2019 at 14:31, Konstantin Shvachko
wrote:
> +1 on RC0.
> - Verified signatures
> - Built from sources
> - Ran unit tests
+1 on RC0.
- Verified signatures
- Built from sources
- Ran unit tests for new features
- Checked artifacts on Nexus, made sure the sources are present.
Thanks
--Konstantin
On Wed, Oct 16, 2019 at 6:01 PM Jonathan Hung wrote:
> Hi folks,
>
> This is the first release candidate for the first
11 matches
Mail list logo
