We should avoid turning this into a replay of Apache Hadoop 2.6.0 (and
to a lesser degree, 2.7.0 and 2.8.0) where a bunch of last minute
“experimental” features derail stability for a significantly long period of
time.
-
Sailesh Patel created HDFS-12339:
Summary: NFS Gateway on Shutdown Gives Unregistration Failure.
Does Not Unregister with rpcbind Portmapper
Key: HDFS-12339
URL: https://issues.apache.org/jira/browse/HDFS-12339
Xiaoyu Yao created HDFS-12338:
-
Summary: Ozone: SCM: clean up containers that timeout during
creation
Key: HDFS-12338
URL: https://issues.apache.org/jira/browse/HDFS-12338
Project: Hadoop HDFS
I
On 8/22/17 3:20 AM, Steve Loughran wrote:
On 21 Aug 2017, at 22:22, Vinod Kumar Vavilapalli wrote:
Steve,
You can be strict & ruthless about the timelines. Anything that doesn’t get in
by mid-September, as was originally planned, can move to the next release - whether
it is feature work on
Such a great community effort - hats off, team!
Thanks
+Vinod
> On Aug 21, 2017, at 11:32 PM, Vrushali Channapattan
> wrote:
>
> Hi folks,
>
> Per earlier discussion [1], I'd like to start a formal vote to merge
> feature branch YARN-5355 [2] (Timeline Service v.2) to trunk. The vote will
> r
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/500/
[Aug 21, 2017 6:08:38 PM] (manojpec) HDFS-11988. Verify HDFS Snapshots with
open files captured are
[Aug 21, 2017 6:48:51 PM] (arp) HDFS-12325. SFTPFileSystem operations should
restore cwd. Contributed by
Mukul Kumar Singh created HDFS-12337:
Summary: Ozone: Concurrent RocksDB open calls fail because of "No
locks available"
Key: HDFS-12337
URL: https://issues.apache.org/jira/browse/HDFS-12337
Proje
Wellington Chevreuil created HDFS-12336:
---
Summary: Listing encryption zones still fails when deleted EZ is
not a direct child of snapshottable directory
Key: HDFS-12336
URL: https://issues.apache.org/jira/br
> On 21 Aug 2017, at 22:22, Vinod Kumar Vavilapalli wrote:
>
> Steve,
>
> You can be strict & ruthless about the timelines. Anything that doesn’t get
> in by mid-September, as was originally planned, can move to the next release
> - whether it is feature work on branches or feature work on tr
