Hi folks,

We're planning on releasing 3.0.0-alpha3 next month (May 15th). The biggest
piece of work targeted for this release is completing user-facing erasure
coding changes. This is on track, but there are some other blockers that we
also need to push on.

I've also written a new status update on the wiki, also reproduced below.

https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+3+release+status+updates

Thanks everyone for their hard work thus far!

Best,
Andrew

================

Red flags:

   - Less than a month out and some new blockers just surfaced, need to
   keep pushing.

Miscellaneous blockers

   - HADOOP-14284 <https://issues.apache.org/jira/browse/HADOOP-14284> (Shade
   Guava everywhere): Progressing, though trying to resolve Curator issues
   - HADOOP-13363 <https://issues.apache.org/jira/browse/HADOOP-13363> (Upgrade
   to protobuf 3): Waiting on the Guava shading first
   - HADOOP-14330 (Kerby breaks multiple SPN support): uncovered from
   secure testing with Oozie, unknown if other Kerby bugs are lurking
   - YARN-5894 (fst licensing): no assignee yet

alpha3 features:

   - Erasure coding
      - Good burndown of remaining blockers for alpha3, seems on track
      - HDFS-11643 (Balancer fencing fails when writing erasure coded lock
      file): Close to commit
      - HDFS-11644 (DFSStripedOutputStream should not implement Syncable):
      API-related issue that affects YARN and HBase

beta1 features:

   - Addressing incompatible changes
      - YARN-6142 (compatibility with 2.x): Still need automated testing
      for this
      - HDFS-11096 (compatibility with 2.x): Still need automated testing
      for this
   - Classpath isolation (HADOOP-11656)
      - Sean has not yet resumed work, but still plans to complete
      API-related subtasks before alpha3
   - Compat guide (HADOOP-13714
   <https://issues.apache.org/jira/browse/HADOOP-13714>)
      - Daniel has started working on this

Reply via email to