[DISCUSS] Release 3.0.4 or branch-3.0 EOL

Hi folks, In branch-3.0, it is almost a year since 3.0.3 was released. Is there any committer who wants to be a release manager of 3.0.4? If there are no users running Apache Hadoop 3.0.x in production, I'm thinking we can stop maintaining branch-3.0. Please let me know there are any users

Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86

For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/1139/ [May 16, 2019 4:26:48 AM] (sunilg) SUBMARINE-56. Update documentation to describe single-node PyTorch [May 16, 2019 1:08:52 PM] (shashikant) HDDS-1531. Disable the sync flag by default during chunk

Re: [DISCUSS] Release 3.0.4 or branch-3.0 EOL

Thanks for initiating the discussion, Akira. I've given similar thoughts on the possible EOL of Hadoop branch-3.0 line. IMHO, I'd love to see HDFS-13596 fixed to make it possible to rolling upgrade from Hadoop 2 to Hadoop 3.0, and then roll

Apache Hadoop qbt Report: branch2+JDK7 on Linux/x86

For more details, see https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/324/ No changes -1 overall The following subsystems voted -1: asflicense findbugs hadolint pathlen unit xml The following subsystems voted -1 but were configured to be filtered/ignored: cc

[jira] [Created] (HADOOP-16319) ITestS3AMiscOperations.testEmptyFileChecksums and ITestS3AMiscOperations.testNonEmptyFileChecksumsUnencrypted fail with default encryption enabled on bucket

Ben Roling created HADOOP-16319: --- Summary: ITestS3AMiscOperations.testEmptyFileChecksums and ITestS3AMiscOperations.testNonEmptyFileChecksumsUnencrypted fail with default encryption enabled on bucket Key: HADOOP-16319

[jira] [Created] (HADOOP-16320) Workaround bug with commons-configuration to be able to emit Ganglia metrics to multiple sink servers

Thomas Poepping created HADOOP-16320: Summary: Workaround bug with commons-configuration to be able to emit Ganglia metrics to multiple sink servers Key: HADOOP-16320 URL: