Re: [DISCUSS] Hadoop-3.2.1 release proposal

On Tue, 20 Aug 2019 at 22:28, Wei-Chiu Chuang wrote: > Hi Rohith, > Thanks for initiating this. > I want to bring up one blocker issue: HDFS-13596 > (NN restart fails > after RollingUpgrade from 2.x to 3.x) > > This should be a blocker for all a

[Release Plan] Hadoop-3.1.3 discussion

Hi folks, We have Apache Hadoop 3.1.2 released on Feb 2019. It's been more than 6 months passed and there're 246 fixes[1]. 2 blocker and 4 critical Issues [2] (As Wei-Chiu Chuang mentioned, HDFS-13596 will be another blocker) I propose my plan to do a maintenance release of 3.1.3 in the next

Re: Thoughts about moving submarine to a separate git repo?

Hi Xun, Thanks for starting this thread. I'm glad to see the existing momentum made by Submarine community, and I like the proposal to make it be a separate Git repo. Some suggestions: 1) For options mentioned by Sunil: I think it's better to be a separate Git repo instead of a branch. To me, th

Re: [VOTE] Mark 2.6, 2.7, 3.0 release lines EOL

+1. Thanks! Jonathan Hung On Tue, Aug 20, 2019 at 8:03 PM Wangda Tan wrote: > Hi all, > > This is a vote thread to mark any versions smaller than 2.7 (inclusive), > and 3.0 EOL. This is based on discussions of [1] > > This discussion runs for 7 days and will conclude on Aug 28 Wed. > > Please

[VOTE] Mark 2.6, 2.7, 3.0 release lines EOL

Hi all, This is a vote thread to mark any versions smaller than 2.7 (inclusive), and 3.0 EOL. This is based on discussions of [1] This discussion runs for 7 days and will conclude on Aug 28 Wed. Please feel free to share your thoughts. Thanks, Wangda [1] http://mail-archives.apache.org/mod_mbo

Re: Make EOL branches to public?

Thank you all for suggestions. Let me send a vote email to mark 2.6, 2.7, 3.0 EOL. - Wangda On Wed, Aug 21, 2019 at 9:34 AM Akira Ajisaka wrote: > +1 > > Thank you for the discussion. > > -Akira > > On Wed, Aug 21, 2019 at 5:51 AM Wei-Chiu Chuang > wrote: > > > > +1 > > I feel like one year of

Re: Make EOL branches to public?

+1 Thank you for the discussion. -Akira On Wed, Aug 21, 2019 at 5:51 AM Wei-Chiu Chuang wrote: > > +1 > I feel like one year of inactivity is a good sign that the community is not > interested in the branch any more. > > On Fri, Aug 16, 2019 at 3:14 AM Wangda Tan wrote: > > > Hi folks, > > > >

Re: Make EOL branches to public?

+1 I feel like one year of inactivity is a good sign that the community is not interested in the branch any more. On Fri, Aug 16, 2019 at 3:14 AM Wangda Tan wrote: > Hi folks, > > Want to hear your thoughts about what we should do to make some branches > EOL. We discussed a couple of times befor

[jira] [Resolved] (HADOOP-16523) Minor spell mistake in comment (PR#388)

[ https://issues.apache.org/jira/browse/HADOOP-16523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang resolved HADOOP-16523. -- Fix Version/s: 3.3.0 Resolution: Fixed > Minor spell mistake in comment (PR#38

[jira] [Created] (HADOOP-16523) Minor spell mistake in comment (PR#388)

Wei-Chiu Chuang created HADOOP-16523: Summary: Minor spell mistake in comment (PR#388) Key: HADOOP-16523 URL: https://issues.apache.org/jira/browse/HADOOP-16523 Project: Hadoop Common Iss

Re: Hadoop Community Sync Up Schedule

Hi Wangda, thanks for this. A question about the schedule correction: > > 1) In the proposal, repeats are not properly. (I used bi-weekly instead of > 2nd/4th week as repeat frequency). I'd like to fix the frequency on Thu and > it will take effect starting next week. I understand that “bi-weekly

Re: Make EOL branches to public?

For what it's worth, in HBase we've been approximating which Hadoop lines are EOL by looking at release rates and specifically CVE announcements that include an affected release line but do not include a fix for that release line. Our current approximation[1] lists 2.6, 2.7, and 3.0 as dead. So tha

Re: [DISCUSS] move storage community online sync schedule

I don't see an objection so let's move to 10AM US Pacific Daylight Saving Time (UTC-7) starting this Wednesday. I'll update the relevant information. Further reminder, Konstantin will talk about NameNode Fine-Grained Locking. Please let me know if you have any feedbacks and ideas to share. Is the

Re: [DISCUSS] Hadoop-3.2.1 release proposal

Hi Rohith, Thanks for initiating this. I want to bring up one blocker issue: HDFS-13596 (NN restart fails after RollingUpgrade from 2.x to 3.x) This should be a blocker for all active Hadoop 3.x releases: 3.3.0, 3.2.1, 3.1.3. Hopefully we can get

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

For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/1234/ [Aug 19, 2019 5:47:49 PM] (hanishakoneru) HDDS-1105 : Add mechanism in Recon to obtain DB snapshot 'delta' updates [Aug 19, 2019 6:12:09 PM] (weichiu) HADOOP-14784. [KMS] Improve KeyAuthorizationKeyProvid

[jira] [Created] (HADOOP-16522) Encrypt buffered data on disk

Mike Yoder created HADOOP-16522: --- Summary: Encrypt buffered data on disk Key: HADOOP-16522 URL: https://issues.apache.org/jira/browse/HADOOP-16522 Project: Hadoop Common Issue Type: Sub-task

[jira] [Resolved] (HADOOP-16521) Subject has a contradiction between proxy user and real user

[ https://issues.apache.org/jira/browse/HADOOP-16521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daryn Sharp resolved HADOOP-16521. -- Resolution: Invalid > Subject has a contradiction between proxy user and real user >

Re: Hadoop Community Sync Up Schedule

+1 On Mon, Aug 19, 2019 at 8:32 PM Wangda Tan wrote: > Hi folks, > > We have run community sync up for 1.5 months. I spoke to folks offline and > got some feedback. Here's a summary of what I've observed from sync ups and > talked to organizers. > > Following sync ups have very good participants

Re: Thoughts about moving submarine to a separate git repo?

> > > > Submarine dev community has a total of 8 developers and submits an average > of 4 to 5 PR per day. > But there are a limited number of Hadoop committer actively help review and > merge patches, which causes development progress delays. > > I just want to point this out that this is concerni

Re: Thoughts about moving submarine to a separate git repo?

+1 (non-binding) We need a separate repository to keep it quickly development. On Tue, Aug 20, 2019 at 3:00 PM zac yuan wrote: > +1 (non-binding) > Looking forward to having a separate repo and making the development more > conveniently and rapidly. > > Thanks > Zac Zhou > > kevin su 于2019年8月2

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

For more details, see https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/419/ [Aug 19, 2019 2:01:12 AM] (weichiu) HDFS-13101. Yet another fsimage corruption related to snapshot. -1 overall The following subsystems voted -1: asflicense findbugs hadolint pathlen unit xml

Re: Hadoop Community Sync Up Schedule

Hi Wangda, Thank you for continuing to keep us moving forward and refining these vital sync-ups. > 3) Update the US [YARN/MapReduce] sync up time from 9AM to 10AM PDT. That puts it at noon central time, which is during our lunch hour. However, I am +1 for this if we are able to allow greater pa

[DISCUSS] Hadoop-3.2.1 release proposal

Hello folks, It's been more than six month Hadoop-3.2.0 is released i.e 16th Jan,2019. We have several important fixes landed in branch-3.2 (around 48 blockers/critical https://s.apache.org/ozd6o). I am planning to do a maintenance release of 3.2.1 in next few weeks i.e around 1st week of Septemb

Re: Hadoop storage community online sync

Great question! Currently Pacific Daylight Saving Time is UTC-7, and Pacific Standard Time, UTC-8 doesn't start until November 3rd. I am being too US-centric, but if the purpose is to invite more people, where many of them are US west coast based, we should do this following the US pacific time zon