hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Wang <andrew.w...@cloudera.com>
Subject Re: [VOTE] Release Apache Hadoop 3.0.0-alpha4-RC0
Date Fri, 30 Jun 2017 16:29:42 GMT
Thanks for taking a look Steve,

On Fri, Jun 30, 2017 at 4:59 AM, Steve Loughran <stevel@hortonworks.com>
wrote:

>
> On 30 Jun 2017, at 03:40, Andrew Wang <andrew.wang@cloudera.com> wrote:
>
> Hi all,
>
> As always, thanks to the many, many contributors who helped with this
> release! I've prepared an RC0 for 3.0.0-alpha4:
>
> http://home.apache.org/~wang/3.0.0-alpha4-RC0/
>
>
> whats the git commit ID? or signed tag?
>

I'd already pushed a signed tag per the HowToRelease instructions, LMK if
it's not right.

>
>
> The standard 5-day vote would run until midnight on Tuesday, July 4th.
> Given that July 4th is a holiday in the US, I expect this vote might have
> to be extended, but I'd like to close the vote relatively soon after.
>
> I've done my traditional testing of a pseudo-distributed cluster with a
> single task pi job, which was successful.
>
> Normally my testing would end there, but I'm slightly more confident this
> time. At Cloudera, we've successfully packaged and deployed a snapshot from
> a few days ago, and run basic smoke tests. Some bugs found from this
> include HDFS-11956, which fixes backwards compat with Hadoop 2 clients, and
> the revert of HDFS-11696, which broke NN QJM HA setup.
>
> Vijay is working on a test run with a fuller test suite (the results of
> which we can hopefully post soon).
>
> My +1 to start,
>
> Best,
> Andrew
>
>
>
> I haven't tested with this alpha, but spark 2.2+ can't read files on
> Azure: https://issues.apache.org/jira/browse/HADOOP-14598
>
> Cause: https://issues.apache.org/jira/browse/HADOOP-14383
>
> I can see how to do a test we can put into hadoop-common (for trunk/2.9);
> if the bug exists in this RC then I think we'll need to revert the
> HADOOP-14598 patch for now & then work on a fix
>
> Sorry —only discovered it this week...an unexpected combination of
> features which only become visible when you take the latest bits of two
> projects and then run some blobstore tests downstream (https://github.com/
> hortonworks-spark/cloud-integration/tree/master/cloud-examples/)
>
> Ick, I somehow didn't see this blocker on the release dashboard for
alpha4, but seems like it's targeted now.

If it only affects WASB, then I think we can get by without it for the
alpha, fix it in beta1. WDYT?

Best,
Andrew

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message