Chen Liang created HDFS-12793:
-
Summary: Ozone : TestSCMCli is failing consistently
Key: HDFS-12793
URL: https://issues.apache.org/jira/browse/HDFS-12793
Project: Hadoop HDFS
Issue Type: Bug
For more details, see
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/34/
[Nov 7, 2017 8:15:53 PM] (brahma) HDFS-12783. [branch-2] dfsrouter should use
hdfsScript. Contributed by
-1 overall
The following subsystems voted -1:
asflicense unit xml
The following subsyste
A related point - I thought I mentioned this in one of the release preparation
threads, but in any case.
Starting 2.7.0, for every .0 release, we've been adding a disclaimer (to the
voting thread as well as the final release) that the first release can
potentially go through additional fixes to
Íñigo Goiri created HDFS-12792:
--
Summary: RBF: Test Router-based federation using HDFSContract
Key: HDFS-12792
URL: https://issues.apache.org/jira/browse/HDFS-12792
Project: Hadoop HDFS
Issue Ty
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/584/
[Nov 7, 2017 10:53:48 PM] (templedf) YARN-7401. Reduce lock contention in
[Nov 8, 2017 12:39:04 AM] (wang) HADOOP-15018. Update JAVA_HOME in
create-release for Xenial Dockerfile.
[Nov 8, 2017 2:22:13 AM] (w
Mukul Kumar Singh created HDFS-12791:
Summary: NameNode Fsck http Connection can timeout for directories
with multiple levels
Key: HDFS-12791
URL: https://issues.apache.org/jira/browse/HDFS-12791
Rakesh R created HDFS-12790:
---
Summary: [SPS]: Rebasing HDFS-10285 branch after HDFS-10467,
HDFS-12599 and HDFS-11968 commits
Key: HDFS-12790
URL: https://issues.apache.org/jira/browse/HDFS-12790
Project: Ha
> On 7 Nov 2017, at 19:08, Vinod Kumar Vavilapalli wrote:
>
>
>
>
>> Frankly speaking, working on some bridging release not targeting any feature
>> isn't so attractive to me as a contributor. Overall, the final minor release
>> off branch-2 is good, we should also give 3.x more time to evo
We are canceling the RC due to the issue that Rohith/Sunil identified. The
issue was difficult to track down as it only happens when you use IP for ZK
(works fine with host names) and moreover if ZK and RM are co-located on
same machine. We are hopeful to get the fix in tomorrow and roll out RC1.