[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,

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]

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

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

[jira] [Created] (YARN-9768) RM Renew Delegation token thread should timeout and retry

CR Hota created YARN-9768: - Summary: RM Renew Delegation token thread should timeout and retry Key: YARN-9768 URL: https://issues.apache.org/jira/browse/YARN-9768 Project: Hadoop YARN Issue Type:

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

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

[jira] [Created] (YARN-9767) PartitionQueueMetrics Issues

Manikandan R created YARN-9767: -- Summary: PartitionQueueMetrics Issues Key: YARN-9767 URL: https://issues.apache.org/jira/browse/YARN-9767 Project: Hadoop YARN Issue Type: Bug

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

[jira] [Created] (YARN-9766) YARN CapacityScheduler QueueMetrics has missing metrics for parent queues having same name

Tarun Parimi created YARN-9766: -- Summary: YARN CapacityScheduler QueueMetrics has missing metrics for parent queues having same name Key: YARN-9766 URL: https://issues.apache.org/jira/browse/YARN-9766

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

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

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

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

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

[jira] [Created] (YARN-9765) SLS runner crashes when run with metrics turned off.

Abhishek Modi created YARN-9765: --- Summary: SLS runner crashes when run with metrics turned off. Key: YARN-9765 URL: https://issues.apache.org/jira/browse/YARN-9765 Project: Hadoop YARN Issue

[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

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

+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月20日周二 下午2:45写道： > +1, Agree > using separate repo can better develop and maintain submarine > > Xun Liu 於 2019年8月20日 週二 下午2:05寫道： > > > Hi

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

+1, Agree using separate repo can better develop and maintain submarine Xun Liu 於 2019年8月20日 週二 下午2:05寫道： > Hi Sunil > > Thank you for your advice and attention. > > The Hadoop submarine development team needs a separate repo for several > reasons: > 1. We have developed a separate submarine

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

Hi Sunil Thank you for your advice and attention. The Hadoop submarine development team needs a separate repo for several reasons: 1. We have developed a separate submarine website to introduce the functions and features of submarine. The common practice is to put it in the gh-pages branch of