See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/1217/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 8474 lines...]
Running
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/1216/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 9072 lines...]
Tests run: 10, Failures: 0,
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/3139/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 43231 lines...]
Running
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/1215/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 8470 lines...]
Tests run: 6, Failures: 1,
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/1214/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 9590 lines...]
Tests run: 2, Failures: 0,
As I expressed on HDFS-8791, I do not want to include this JIRA in a
maintenance release. I've only seen it crop up on a handful of our
customer's clusters, and large users like Twitter and Yahoo that seem to be
more affected are also the most able to patch this change in themselves.
Layout
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/3137/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 31866 lines...]
Tests run: 13, Failures: 0, Errors:
As of 2 days ago, there were already 135 jiras associated with 2.7.3,
if *any* of them end up introducing a regression the inclusion of
HDFS-8791 means that folks will have cluster downtime in order to back
things out. If that happens to any substantial number of downstream
folks, or any
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/1213/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 8470 lines...]
Running
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/1212/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 8468 lines...]
Running
Thanks for bringing up this topic, Sean.
When I released our latest Hadoop release 2.6.4, the patch of HDFS-8791 haven't
been committed in so that's why we didn't discuss this earlier.
I remember in JIRA discussion, we treated this layout change as a Blocker bug
that fixing a significant
A layout change in a maintenance release sounds very risky. I saw some
discussion on the JIRA about those risks, but the consensus seemed to
be "we'll leave it up to the 2.6 and 2.7 release managers." I thought
we did RMs per release rather than per branch? No one claiming to be a
release manager
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/3136/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 31980 lines...]
Tests run: 2, Failures: 0, Errors:
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/1211/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 9551 lines...]
Tests run: 2, Failures: 0,
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/3135/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 31993 lines...]
Tests run: 11, Failures: 0, Errors:
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/1210/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 8815 lines...]
Running
Thank you Vinod!
FYI: 2.7.3 will be a bit special release.
HDFS-8791 bumped up the datanode layout version,
so rolling downgrade from 2.7.3 to 2.7.[0-2]
is impossible. We can rollback instead.
https://issues.apache.org/jira/browse/HDFS-8791
17 matches
Mail list logo
