[DISCUSS] Enable github security notifications to all Hadoop committers

Hi, I raised INFRA-19327 to enable github security notification. How do people feel if we enable this notification to all committers? I already have hundreds of incoming emails from various Hadoop alias each day so I don't mind adding a few more.

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

For more details, see https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/484/ No changes - To unsubscribe, e-mail: mapreduce-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-dev-h...@had

Re: [VOTE] Release Apache Hadoop 2.10.0 (RC1)

+1 on RC1 - Verified signatures - Verified maven artifacts on Nexus for sources - Checked rat reports - Checked documentation - Checked packaging contents - Built from sources on RHEL 7 box - Ran unit tests for new HDFS features with Java 8 Thanks, --Konstantin On Tue, Oct 22, 2019 at 2:55 PM Jo

Re: [Discuss] Hadoop-Ozone repository mailing list configurations

We're going to fix the Submarine email list issues once spin-off works start On Wed, Oct 23, 2019 at 2:39 PM Matt Foley wrote: > Definitely yes on ‘ozone-issues’. Whether we want to keep ozone-dev and > hdfs-dev together or separate, I’m neutral. > Thanks, > —Matt > > On Oct 23, 2019, at 2:11 P

Re: [Discuss] Hadoop-Ozone repository mailing list configurations

Definitely yes on ‘ozone-issues’. Whether we want to keep ozone-dev and hdfs-dev together or separate, I’m neutral. Thanks, —Matt On Oct 23, 2019, at 2:11 PM, Elek, Marton wrote: Thanks to report this problem Rohith, Yes, it seems to be configured with the wrong mailing list. I think the rig

Re: [Discuss] Hadoop-Ozone repository mailing list configurations

Thanks to report this problem Rohith, Yes, it seems to be configured with the wrong mailing list. I think the right fix is to create ozone-dev@ and ozone-issues@ and use them instead of hdfs-(dev/issues). Is there any objections against creating new ozone-* mailing lists? Thanks, Marton On

Re: [VOTE] Release Apache Hadoop 2.10.0 (RC1)

Hi Eric, thanks for trying it out. We talked about this in today's YARN community sync up, summarizing here for everyone else: I don't think it's worth delaying the 2.10.0 release further, we can address this in a subsequent 2.10.x release. Wangda mentioned it might be related to changes in domina

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

For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/1298/ [Oct 22, 2019 1:04:02 PM] (ayushsaxena) HDFS-14918. Remove useless getRedundancyThread from [Oct 22, 2019 1:14:22 PM] (ayushsaxena) HDFS-14915. Move Superuser Check Before Taking Lock For Encryption API.

Re: [VOTE] Release Apache Hadoop 2.10.0 (RC1)

Hi Jonathan, Thanks very much for all of your work on this release. I have a concern about cross-queue (inter-queue) preemption in 2.10. In 2.8, on a 6 node pseudo-cluster, preempting from one queue to meet the needs of another queue seems to work as expected. However, 2.10 in the same pseudo-