[jira] [Resolved] (YARN-2097) Documentation: health check return status

[ https://issues.apache.org/jira/browse/YARN-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YARN-2097. Resolution: Won't Fix > Documentation: health check return sta

[jira] [Resolved] (YARN-2345) yarn rmadmin -report

[ https://issues.apache.org/jira/browse/YARN-2345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YARN-2345. Resolution: Won't Fix > yarn rmadmin -report > > >

[jira] [Resolved] (YARN-2429) LCE should blacklist based upon group

[ https://issues.apache.org/jira/browse/YARN-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YARN-2429. Resolution: Won't Fix > LCE should blacklist based upon gr

[jira] [Resolved] (YARN-2471) DEFAULT_YARN_APPLICATION_CLASSPATH doesn't honor hadoop-layout.sh

[ https://issues.apache.org/jira/browse/YARN-2471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YARN-2471. Resolution: Won't Fix > DEFAULT_YARN_APPLICATION_CLASSPATH doesn't honor hadoop-layout

[jira] [Resolved] (YARN-2413) capacity scheduler will overallocate vcores

[ https://issues.apache.org/jira/browse/YARN-2413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YARN-2413. Resolution: Won't Fix > capacity scheduler will overallocate vco

[jira] [Resolved] (YARN-2806) log container allocation requests

[ https://issues.apache.org/jira/browse/YARN-2806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YARN-2806. Resolution: Won't Fix > log container allocation reque

[jira] [Resolved] (YARN-3175) Consolidate the ResournceManager documentation into one

[ https://issues.apache.org/jira/browse/YARN-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YARN-3175. Resolution: Won't Fix > Consolidate the ResournceManager documentation into

[jira] [Resolved] (YARN-3484) Fix up yarn top shell code

[ https://issues.apache.org/jira/browse/YARN-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YARN-3484. Resolution: Won't Fix Target Version/s: (was: ) > Fix up yarn top shell c

[jira] [Resolved] (YARN-4432) yarn launch script works by chance

[ https://issues.apache.org/jira/browse/YARN-4432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YARN-4432. Resolution: Won't Fix > yarn launch script works by cha

[jira] [Resolved] (YARN-5099) hadoop-yarn unit tests for dynamic commands

[ https://issues.apache.org/jira/browse/YARN-5099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YARN-5099. Resolution: Won't Fix > hadoop-yarn unit tests for dynamic comma

[jira] [Resolved] (YARN-5064) move the shell code out of hadoop-yarn

[ https://issues.apache.org/jira/browse/YARN-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YARN-5064. Resolution: Won't Fix > move the shell code out of hadoop-y

[jira] [Resolved] (YARN-5530) YARN dependencies are a complete mess

[ https://issues.apache.org/jira/browse/YARN-5530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YARN-5530. Resolution: Won't Fix > YARN dependencies are a complete m

[jira] [Resolved] (YARN-5454) Various places have a hard-coded location for bash

[ https://issues.apache.org/jira/browse/YARN-5454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YARN-5454. Resolution: Won't Fix > Various places have a hard-coded location for b

[jira] [Resolved] (YARN-5635) Better handling when bad script is configured as Node's HealthScript

[ https://issues.apache.org/jira/browse/YARN-5635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YARN-5635. Resolution: Won't Fix > Better handling when bad script is configured as Nod

[jira] [Resolved] (YARN-6241) Remove -jt flag

[ https://issues.apache.org/jira/browse/YARN-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YARN-6241. Resolution: Won't Fix > Remove -jt flag > --- > >

[jira] [Resolved] (YARN-6452) test-container-executor should not be in bin in dist tarball

[ https://issues.apache.org/jira/browse/YARN-6452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YARN-6452. Resolution: Won't Fix > test-container-executor should not be in bin in dist tarb

[jira] [Resolved] (YARN-7588) Remove 'yarn historyserver' from bin/yarn

[ https://issues.apache.org/jira/browse/YARN-7588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YARN-7588. Resolution: Won't Fix > Remove 'yarn historyserver' from bin/y

Re: [DISCUSS] Alpha Release of Ozone

> On Aug 8, 2018, at 12:56 PM, Anu Engineer wrote: > >> Has anyone verified that a Hadoop release doesn't have _any_ of the extra >> ozone bits that are sprinkled outside the maven modules? > As far as I know that is the state, we have had multiple Hadoop releases > after ozone has been

Re: [DISCUSS] Alpha Release of Ozone

Given that there are some Ozone components spread out past the core maven modules, is the plan to release a Hadoop Trunk + Ozone tar ball or is more work going to go into segregating the Ozone components prior to release? Has anyone verified that a Hadoop release doesn't have _any_ of the

Re: [VOTE] Release Apache Hadoop 3.0.3 (RC0)

> On Jun 7, 2018, at 11:47 AM, Steve Loughran wrote: > > Actually, Yongjun has been really good at helping me get set up for a 2.7.7 > release, including "things you need to do to get GPG working in the docker > image” *shrugs* I use a different release script after some changes broke

Re: [VOTE] Release Apache Hadoop 3.0.3 (RC0)

> On Jun 7, 2018, at 3:46 AM, Lokesh Jain wrote: > > Hi Yongjun > > I followed Nanda’s steps and I see the same issues as reported by Nanda. This situation is looking like an excellent opportunity for PMC members to mentor people on how the build works since it’s apparent that three days

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

> On May 15, 2018, at 10:16 AM, Chris Douglas wrote: > > They've been failing for a long time. It can't install bats, and > that's fatal? -C The bats error is new and causes the build to fail enough that it produces the email output. For the past few months, it

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

FYI: I’m going to disable the branch-2 nightly jobs. - To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org

Re: [NOTIFICATION] Hadoop trunk rebased

Did the patch that fixes the mountain of maven warnings get missed? > On Apr 26, 2018, at 11:52 PM, Akira Ajisaka wrote: > > + common-dev and mapreduce-dev > > On 2018/04/27 6:23, Owen O'Malley wrote: >> As we discussed in hdfs-dev@hadoop, I did a force push to Hadoop's

Fwd: Apache Hadoop qbt Report: trunk+JDK8 on Windows/x64

For my part of the HDFS bug bash, I’ve gotten the ASF Windows build working again. Starting tomorrow, results will be sent to the *-dev lists. A few notes: * It only runs the unit tests. There’s not much point in running the other Yetus plugins since those are covered by the Linux

Re: [ANNOUNCE] Apache Hadoop 3.0.0 GA is released

It’s significantly more concerning that 3.0.0-beta1 doesn’t show up here: http://hadoop.apache.org/docs/r3.0.0/hadoop-project-dist/hadoop-common/release/index.html It looks like they are missing from the source tag too. I wonder what else is missing. > On Dec 18, 2017, at 11:15 AM, Andrew

[jira] [Created] (YARN-7588) Remove 'yarn historyserver' from bin/yarn

Allen Wittenauer created YARN-7588: -- Summary: Remove 'yarn historyserver' from bin/yarn Key: YARN-7588 URL: https://issues.apache.org/jira/browse/YARN-7588 Project: Hadoop YARN Issue Type

Re: [VOTE] Release Apache Hadoop 3.0.0 RC0

> On Nov 30, 2017, at 1:07 AM, Rohith Sharma K S > wrote: > > > >. If ATSv1 isn’t replaced by ATSv2, then why is it marked deprecated? > Ideally it should not be. Can you point out where it is marked as deprecated? > If it is in historyserver daemon start, that

Re: [VOTE] Release Apache Hadoop 3.0.0 RC0

> On Nov 21, 2017, at 2:16 PM, Vinod Kumar Vavilapalli > wrote: > >>> - $HADOOP_YARN_HOME/sbin/yarn-daemon.sh start historyserver doesn't even >>> work. Not just deprecated in favor of timelineserver as was advertised. >> >> This works for me in trunk and the bash

Re: [VOTE] Release Apache Hadoop 3.0.0 RC0

The original release script and instructions broke the build up into three or so steps. When I rewrote it, I kept that same model. It’s probably time to re-think that. In particular, it should probably be one big step that even does the maven deploy. There’s really no harm in doing

Re: [DISCUSSION] Merging HDFS-7240 Object Store (Ozone) to trunk

> On Nov 3, 2017, at 12:08 PM, Stack wrote: > > On Sat, Oct 28, 2017 at 2:00 PM, Konstantin Shvachko > wrote: > >> It is an interesting question whether Ozone should be a part of Hadoop. > > I don't see a direct answer to this question. Is there one?

[jira] [Created] (YARN-7432) DominantResourceFairnessPolicy serializable findbugs issues

Allen Wittenauer created YARN-7432: -- Summary: DominantResourceFairnessPolicy serializable findbugs issues Key: YARN-7432 URL: https://issues.apache.org/jira/browse/YARN-7432 Project: Hadoop YARN

[jira] [Created] (YARN-7431) resource estimator has findbugs problems

Allen Wittenauer created YARN-7431: -- Summary: resource estimator has findbugs problems Key: YARN-7431 URL: https://issues.apache.org/jira/browse/YARN-7431 Project: Hadoop YARN Issue Type

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

> On Oct 24, 2017, at 4:10 PM, Andrew Wang wrote: > > FWIW we've been running branch-3.0 unit tests successfully internally, though > we have separate jobs for Common, HDFS, YARN, and MR. The failures here are > probably a property of running everything in the same

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

omments and it >> even cannot tell which daemons/components of HDFS consumes unexpected high >> memory. Don't sounds like a solid bug report to me. >> >> >> >> Thanks,? >> >> >> Junping >> >> >> _

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

> On Oct 23, 2017, at 12:50 PM, Allen Wittenauer <a...@effectivemachines.com> > wrote: > > > > With no other information or access to go on, my current hunch is that one of > the HDFS unit tests is ballooning in memory size. The easiest way to kill a &g

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

est > failures/timeout. > > Thanks, > Subru > > On Mon, Oct 23, 2017 at 11:26 AM, Vrushali C <vrushalic2...@gmail.com> wrote: > Hi Allen, > > I have filed https://issues.apache.org/jira/browse/YARN-7380 for the > timeline service findbugs warnings.

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

I’m really confused why this causes the Yahoo! QA boxes to go catatonic (!?!) during the run. As in, never come back online, probably in a kernel panic. It’s pretty consistently in hadoop-hdfs, so something is going wrong there… is branch-2 hdfs behaving badly? Someone needs to run the

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

To whoever set this up: There was a job config problem where the Jenkins branch parameter wasn’t passed to Yetus. Therefore both of these reports have been against trunk. I’ve fixed this job (as well as the other jobs) to honor that parameter. I’ve kicked off a new run with these changes.

YARN native services Re: 2017-10-06 Hadoop 3 release status update

> On Oct 6, 2017, at 5:51 PM, Eric Yang wrote: > yarn application -deploy –f spec.json > yarn application -stop > yarn application -restart > yarn application -remove > > and > > yarn application –list will display both application list from RM as well as > docker

Re: 2017-10-06 Hadoop 3 release status update

> On Oct 6, 2017, at 1:31 PM, Andrew Wang wrote: > > - Still waiting on Allen to review YARN native services feature. Fake news. I’m still -1 on it, at least prior to a patch that posted late yesterday. I’ll probably have a chance to play with it

[jira] [Created] (YARN-7227) hadoop personality: yarn-ui should be conditional

Allen Wittenauer created YARN-7227: -- Summary: hadoop personality: yarn-ui should be conditional Key: YARN-7227 URL: https://issues.apache.org/jira/browse/YARN-7227 Project: Hadoop YARN

Re: qbt is failiing///RE: Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86

> On Sep 19, 2017, at 6:35 AM, Brahma Reddy Battula > wrote: > > qbt is failing from two days with following errors, any idea on this..? Nothing to be too concerned about. This is what it looks like when a build server gets bounced or crashed.

Re: [VOTE] Merge yarn-native-services branch into trunk

> On Sep 8, 2017, at 9:25 AM, Jian He wrote: > > Hi Allen, > The documentations are committed. Please check QuickStart.md and others in > the same folder. > YarnCommands.md doc is updated to include new commands. > DNS default port is also documented. > Would you like to

Re: [VOTE] Merge yarn-native-services branch into trunk

> On Sep 5, 2017, at 6:23 PM, Jian He wrote: > >> If it doesn’t have all the bells and whistles, then it shouldn’t be on >> port 53 by default. > Sure, I’ll change the default port to not use 53 and document it. >> *how* is it getting launched on a privileged

Re: [VOTE] Merge yarn-native-services branch into trunk

> On Sep 5, 2017, at 3:12 PM, Gour Saha wrote: > > 2) Lots of markdown problems in the NativeServicesDiscovery.md document. > This includes things like Œyarnsite.xml¹ (missing a dash.) > > The md patch uploaded to YARN-5244 had some special chars. I fixed those > in

Re: [VOTE] Merge yarn-native-services branch into trunk

> On Sep 5, 2017, at 2:53 PM, Jian He wrote: > >> Based on the documentation, this doesn’t appear to be a fully function DNS >> server as an admin would expect (e.g., BIND, Knot, whatever). Where’s >> forwarding? How do I setup notify? Are secondaries even supported?

Re: [VOTE] Merge yarn-native-services branch into trunk

> On Aug 31, 2017, at 8:33 PM, Jian He wrote: > I would like to call a vote for merging yarn-native-services to trunk. 1) Did I miss it or is there no actual end-user documentation on how to use this? I see

YARN javadoc failures Re: [DISCUSS] Branches and versions for Hadoop 3

> On Aug 28, 2017, at 9:58 AM, Allen Wittenauer <a...@effectivemachines.com> > wrote: > The automation only goes so far. At least while investigating Yetus > bugs, I've seen more than enough blatant and purposeful ignored errors and > warnings that I'm not convinced

Re: [DISCUSS] Branches and versions for Hadoop 3

> On Aug 28, 2017, at 12:41 PM, Jason Lowe wrote: > > I think this gets back to the "if it's worth committing" part. This brings us back to my original question: "Doesn't this place an undue burden on the contributor with the first incompatible patch to prove

Re: [DISCUSS] Branches and versions for Hadoop 3

> On Aug 25, 2017, at 1:23 PM, Jason Lowe <jl...@oath.com> wrote: > > Allen Wittenauer wrote: > > > Doesn't this place an undue burden on the contributor with the first > > incompatible patch to prove worthiness? What happens if it is decided

Re: [DISCUSS] Branches and versions for Hadoop 3

> On Aug 25, 2017, at 10:36 AM, Andrew Wang wrote: > Until we need to make incompatible changes, there's no need for > a Hadoop 4.0 version. Some questions: Doesn't this place an undue burden on the contributor with the first incompatible patch to prove

[jira] [Resolved] (YARN-7011) yarn-daemon.sh is not respecting --config option

[ https://issues.apache.org/jira/browse/YARN-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YARN-7011. Resolution: Not A Problem Closing this again given the behavior is actually the same given

Re: Branch merges and 3.0.0-beta1 scope

We should avoid turning this into a replay of Apache Hadoop 2.6.0 (and to a lesser degree, 2.7.0 and 2.8.0) where a bunch of last minute “experimental” features derail stability for a significantly long period of time.

[jira] [Resolved] (YARN-7011) yarn-daemon.sh is not respecting --config option

[ https://issues.apache.org/jira/browse/YARN-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YARN-7011. Resolution: Won't Fix Closing as not a bug. Working as designed. > yarn-daemon

Re: Are binary artifacts are part of a release?

ot; > > Thanks, > --Konst > > On Mon, Jul 31, 2017 at 4:51 PM, Allen Wittenauer > <a...@effectivemachines.com> wrote: > > > On Jul 31, 2017, at 4:18 PM, Andrew Wang <andrew.w...@cloudera.com> wrote: > > > > Forking this off to not distract from r

Re: Are binary artifacts are part of a release?

> On Jul 31, 2017, at 4:18 PM, Andrew Wang wrote: > > Forking this off to not distract from release activities. > > I filed https://issues.apache.org/jira/browse/LEGAL-323 to get clarity on the > matter. I read the entire webpage, and it could be improved one way or

Re: [VOTE] Release Apache Hadoop 2.7.4 (RC0)

> On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko > wrote: > > https://wiki.apache.org/hadoop/HowToReleasePreDSBCR FYI: If you are using ASF Jenkins to create an ASF release artifact, it's pretty much an automatic vote failure as any such

Re: Pre-Commit build is failing

gt;> On Fri, Jul 21, 2017 at 6:24 PM, Konstantin Shvachko < > >> shv.had...@gmail.com> wrote: > >> > >>> What stuff? Is there a jira? > >>> It did work like a week ago. Is it a new Yetus requirement. > >>> Anyways I can commit a change t

[jira] [Created] (YARN-6721) container-executor should have -fstack-check

Allen Wittenauer created YARN-6721: -- Summary: container-executor should have -fstack-check Key: YARN-6721 URL: https://issues.apache.org/jira/browse/YARN-6721 Project: Hadoop YARN Issue

[jira] [Created] (YARN-6709) Root privilege escalation in experimental Docker support

Allen Wittenauer created YARN-6709: -- Summary: Root privilege escalation in experimental Docker support Key: YARN-6709 URL: https://issues.apache.org/jira/browse/YARN-6709 Project: Hadoop YARN

[jira] [Resolved] (YARN-6709) Root privilege escalation in experimental Docker support

[ https://issues.apache.org/jira/browse/YARN-6709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YARN-6709. Resolution: Fixed This was fixed as part of a series of commits done via security@hadoop

Re: About 2.7.4 Release

Is there any reason to not Close -alpha1+resolved state JIRAs? It's been quite a while and those definitely should not getting re-opened anymore. What about -alpha2's that are also resolved? - To unsubscribe, e-mail:

Re: About 2.7.4 Release

> On May 1, 2017, at 2:27 PM, Andrew Wang wrote: > I believe I asked about this on dev-yetus a while back. I'd prefer that the > presence of the fix version be sufficient to indicate whether a JIRA is > included in a release branch. Yetus requires that the JIRA be

Re: About 2.7.4 Release

> On Apr 25, 2017, at 12:35 AM, Akira Ajisaka wrote: > > Maybe we should create a jira to track this? > > I think now either way (reopen or create) is fine. > > Release doc maker creates change logs by fetching information from JIRA, so > reopening the tickets should be

Re: HADOOP-14316: Switching from Findbugs to Spotbugs

> On Apr 19, 2017, at 10:52 AM, Wei-Chiu Chuang wrote: > That sounds scary. Would you mind to share the list of bugs that spotbugs > found? Sounds like some of them may warrant new blockers jiras for Hadoop 3. I've added the list to the JIRA.

HADOOP-14316: Switching from Findbugs to Spotbugs

Hey gang. HADOOP-14316 enables the spotbugs back-end for the findbugs front-end. Spotbugs (https://spotbugs.github.io/) is the fork of findbugs that the community and some of the major contributors have made to move findbugs forward. It is geared towards JDK8 and JDK9.

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

Looks like someone reset HEAD back to Mar 31. Sent from my iPad > On Apr 16, 2017, at 12:08 AM, Apache Jenkins Server > wrote: > > For more details, see > https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/378/ > > > > > > -1 overall > > > The

Re: Hadoop QA fails with "Docker failed to build yetus/hadoop:a9ad5d6"

> On Apr 13, 2017, at 11:13 PM, Arun Suresh wrote: > > Yup, > > YARN Pre-Commit tests are having the same problem as well. > Is there anything that can be done to fix this ? Ping Yetus folks (Allen / > Sean) https://issues.apache.org/jira/browse/HADOOP-14311

[jira] [Resolved] (YARN-6449) Enable YARN to accept jobs with < 1 core allocations

[ https://issues.apache.org/jira/browse/YARN-6449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YARN-6449. Resolution: Duplicate > Enable YARN to accept jobs with < 1 core alloc

[jira] [Created] (YARN-6453) fairscheduler-statedump.log gets generated regardless of configured scheduler

Allen Wittenauer created YARN-6453: -- Summary: fairscheduler-statedump.log gets generated regardless of configured scheduler Key: YARN-6453 URL: https://issues.apache.org/jira/browse/YARN-6453

[jira] [Created] (YARN-6452) test-container-executor should not be in bin in dist tarball

Allen Wittenauer created YARN-6452: -- Summary: test-container-executor should not be in bin in dist tarball Key: YARN-6452 URL: https://issues.apache.org/jira/browse/YARN-6452 Project: Hadoop YARN

Re: [DISCUSS] Changing the default class path for clients

ng <andrew.w...@cloudera.com> wrote: > What's the current contract for `hadoop classpath`? Would it be safer to > introduce `hadoop userclasspath` or similar for this behavior? > > I'm betting that changing `hadoop classpath` will lead to some breakages, > so I'd prefer to make t

[DISCUSS] Changing the default class path for clients

This morning I had a bit of a shower thought: With the new shaded hadoop client in 3.0, is there any reason the default classpath should remain the full blown jar list? e.g., shouldn’t ‘hadoop classpath’ just return configuration, user supplied bits (e.g.,

Re: Can we update protobuf's version on trunk?

> On Mar 28, 2017, at 5:09 PM, Chris Douglas wrote: > > I haven't seen data identifying PB as a bottleneck, but the > non-x86/non-Linux and dev setup arguments may make this worthwhile. -C FWIW, we have the same problem with leveldbjni-all. (See the ASF

Re: [RESULT] [VOTE] Release Apache Hadoop 2.8.0 (RC3)

Just a heads up. Looks like some removed the Finish Date off of 2.8.0 in JIRA. It needs to be put back to match what is in the artifacts that we voted on. - To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org For

Re: [VOTE] Release Apache Hadoop 2.8.0 (RC3)

> On Mar 21, 2017, at 10:12 AM, Andrew Wang wrote: > > I poked around a bit. The 3.0.0-alpha2 binary tarball is only 246M and has > more changes than 2.8.0. Not to disclaim any other potential issues, but it's worth noting 3.x de-dupes jar files as part of the

[jira] [Created] (YARN-6365) slsrun.sh creating random html directories

Allen Wittenauer created YARN-6365: -- Summary: slsrun.sh creating random html directories Key: YARN-6365 URL: https://issues.apache.org/jira/browse/YARN-6365 Project: Hadoop YARN Issue Type

Re: About 2.7.4 Release

> On Mar 8, 2017, at 1:54 PM, Allen Wittenauer <a...@effectivemachines.com> > wrote: > > This is already possible: > * don’t use —asfrelease > * use —sign, —native, and, if appropriate for your platform, > —docker and —dockercache

Re: About 2.7.4 Release

> On Mar 8, 2017, at 10:55 AM, Marton Elek wrote: > > I think the main point here is the testing of the release script, not the > creation of the official release. … except the Hadoop PMC was doing exactly this from 2.3.0 up until recently. Which means we have

Re: About 2.7.4 Release

> On Mar 7, 2017, at 2:51 PM, Andrew Wang wrote: > I think it'd be nice to > have a nightly Jenkins job that builds an RC, Just a reminder that any such build cannot be used for an actual release:

[jira] [Created] (YARN-6241) Remove -jt flag

Allen Wittenauer created YARN-6241: -- Summary: Remove -jt flag Key: YARN-6241 URL: https://issues.apache.org/jira/browse/YARN-6241 Project: Hadoop YARN Issue Type: Bug Affects Versions

Re: [VOTE] Release Apache Hadoop 3.0.0-alpha2 RC0

> On Jan 23, 2017, at 8:50 PM, Chris Douglas wrote: > > Thanks for all your work on this, Andrew. It's great to see the 3.x > series moving forward. > > If you were willing to modify the release notes and add the LICENSE to > the jar, we don't need to reset the clock

Re: [VOTE] Release cadence and EOL

> On Jan 21, 2017, at 7:08 PM, Karthik Kambatla wrote: > > 3. RM: some method to madness. Junping, for instance, is trying to roll > a release with 2300 patches. It is a huge time investment. (Thanks again, > Junping.) Smaller releases are easier to manage. A target

Re: [VOTE] Release Apache Hadoop 3.0.0-alpha2 RC0

> On Jan 22, 2017, at 9:05 PM, Allen Wittenauer <a...@effectivemachines.com> > wrote: > > > > > >> On Jan 20, 2017, at 2:36 PM, Andrew Wang <andrew.w...@cloudera.com> wrote: >> >> http://home.apache.org/~wang/3.0.0-alpha2-RC0/ > >

Re: [VOTE] Release Apache Hadoop 3.0.0-alpha2 RC0

> On Jan 20, 2017, at 2:36 PM, Andrew Wang wrote: > > http://home.apache.org/~wang/3.0.0-alpha2-RC0/ There are quite a few JIRA issues that need release notes. - To unsubscribe, e-mail:

Re: [Continued] [Release thread] 2.8.0 release activities

If you ran mvn clean at any point in your repo between create-release and mvn deploy, you'll need to start at running create-release again. create-release leaves things in a state that mvn deploy should be ready to go, with no clean necessary. > On Jan 20, 2017, at 11:12 AM, Junping Du

Re: [VOTE] Release cadence and EOL

> On Jan 18, 2017, at 11:21 AM, Chris Trezzo wrote: > > Thanks Sangjin for pushing this forward! I have a few questions: These are great questions, because I know I'm not seeing a whole lot of substance in this vote. The way to EOL software in the open source

[jira] [Created] (YARN-5848) public/crossdomain.xml is problematic

Allen Wittenauer created YARN-5848: -- Summary: public/crossdomain.xml is problematic Key: YARN-5848 URL: https://issues.apache.org/jira/browse/YARN-5848 Project: Hadoop YARN Issue Type: Bug

[jira] [Created] (YARN-5847) Revert health check exit code check

Allen Wittenauer created YARN-5847: -- Summary: Revert health check exit code check Key: YARN-5847 URL: https://issues.apache.org/jira/browse/YARN-5847 Project: Hadoop YARN Issue Type: Bug

[jira] [Resolved] (YARN-5847) Revert health check exit code check

[ https://issues.apache.org/jira/browse/YARN-5847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YARN-5847. Resolution: Fixed > Revert health check exit code ch

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

> On Oct 6, 2016, at 1:39 PM, Akira Ajisaka wrote: > > > It wasn't 'renamed' to jenkins, prior releases were actually built by and > > on the Jenkins infrastructure. Which was a very very bad idea: it's > > insecure and pretty much against ASF policy. > > Sorry

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

> On Oct 5, 2016, at 10:35 PM, Akira Ajisaka wrote: > Can we rename it? > > AFAIK, hadoop releases were built by hortonmu in 2014 and was renamed to > jenkins. That's not how that works. It's literally storing the id of the person who built the

Re: [Discuss] Merge YARN-3368 to trunk

> On Sep 22, 2016, at 1:24 PM, Wangda Tan wrote: > Actually I'm not trying to debate about if it is necessary to make the UI > project following Hadoop's rules. The answer is always yes to me: we should > follow Hadoop's guide for any of sub project. We're trying to make

Re: [Discuss] Merge YARN-3368 to trunk

> On Sep 22, 2016, at 11:13 AM, Wangda Tan wrote: > >* why are there editor settings and other superfluous things there? do > >these settings comply with the PMC's style guide? why would they be here > >and not in the base of the source tree? > Actually many front-end

Re: [Discuss] Merge YARN-3368 to trunk

On 2016-09-09 15:54 (-0700), Wangda Tan wrote: > We propose to merge YARN-3368 (YARN next generation web UI) development > branch into trunk for better development, would like to hear your thoughts > before sending out vote mail. > A quick pass through the diff: * why are

[RESULTS] Re: [VOTE] Merge HADOOP-13341

The vote passes with 3 +1 binding votes. I'll be merging this later today. Thanks everyone! > On Sep 7, 2016, at 6:44 AM, Allen Wittenauer <a...@effectivemachines.com> > wrote: > > > I’d like to call for a vote to run for 5 days (ending Mon 12, 2016 a

[jira] [Resolved] (YARN-5567) Fix script exit code checking in NodeHealthScriptRunner#reportHealthStatus

[ https://issues.apache.org/jira/browse/YARN-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YARN-5567. Resolution: Fixed > Fix script exit code checking in NodeHealthScriptRun

[jira] [Resolved] (YARN-5635) Revert YARN-5567

[ https://issues.apache.org/jira/browse/YARN-5635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved YARN-5635. Resolution: Fixed Fix Version/s: 3.0.0-alpha2 > Revert YARN-5

[jira] [Created] (YARN-5635) Revert YARN-5567

Allen Wittenauer created YARN-5635: -- Summary: Revert YARN-5567 Key: YARN-5635 URL: https://issues.apache.org/jira/browse/YARN-5635 Project: Hadoop YARN Issue Type: Bug Reporter

  1   2   3   >