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

]. -C [1]: https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/ On Tue, May 15, 2018 at 10:27 AM, Allen Wittenauer <a...@effectivemachines.com> wrote: > >> On May 15, 2018, at 10:16 AM, Chris Douglas <cdoug...@apache.org> wrote: >> >> They've been

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

They've been failing for a long time. It can't install bats, and that's fatal? -C On Tue, May 15, 2018 at 9:43 AM, Allen Wittenauer wrote: > > > FYI: > > I’m going to disable the branch-2 nightly jobs. >

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

Thanks, Allen. On Thu, Mar 15, 2018 at 10:20 AM, Iñigo Goiri wrote: >> * It ALWAYS applies HADOOP-14667.05.patch prior to running. As a result, >> this is only set up for trunk with no parameterization to run other >> branches. I tried to get this running in my environment a

Re: [EVENT] HDFS Bug Bash: March 12

gt; per-meetup-charge issue, but will double check. Let me know if there are > more meetups planned in the near future and we can use this. > > Thanks > +Vinod > > On Mar 6, 2018, at 7:48 PM, Chris Douglas <cdoug...@apache.org> wrote: > > Found a meetup alterna

Re: [EVENT] HDFS Bug Bash: March 12

We're using a shared doc to track work in progress, PA/review ready, and committed [1]. -C [1]: https://s.apache.org/RLlx On Mon, Mar 12, 2018 at 9:17 AM, Chris Douglas <cdoug...@apache.org> wrote: > On Fri, Mar 9, 2018 at 7:52 PM, 俊平堵 <junping...@apache.org> wrote: >>

Re: [EVENT] HDFS Bug Bash: March 12

in the project. -C [1]: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=75965105 > 2018-03-05 16:03 GMT-08:00 Chris Douglas <cdoug...@apache.org>: > >> [Cross-posting, as this affects the rest of the project] >> >> Hey folks- >> >>

Re: [EVENT] HDFS Bug Bash: March 12

ng else I > can help here. > > Thanks, > > Junping > > 2018-03-05 16:03 GMT-08:00 Chris Douglas <cdoug...@apache.org>: > >> [Cross-posting, as this affects the rest of the project] >> >> Hey folks- >> >> As discussed last month [1],

Re: [EVENT] HDFS Bug Bash: March 12

05 On Tue, Mar 6, 2018 at 7:48 PM, Chris Douglas <cdoug...@apache.org> wrote: > Found a meetup alternative (thanks Subru): > https://meetingstar.io/event/fk13172f1d75KN > > So we can get a rough headcount, please add (local) if you plan to > attend in-person. -C > > &g

Re: [EVENT] HDFS Bug Bash: March 12

Found a meetup alternative (thanks Subru): https://meetingstar.io/event/fk13172f1d75KN So we can get a rough headcount, please add (local) if you plan to attend in-person. -C On Mon, Mar 5, 2018 at 4:03 PM, Chris Douglas <cdoug...@apache.org> wrote: > [Cross-posting, as this affects

[EVENT] HDFS Bug Bash: March 12

[Cross-posting, as this affects the rest of the project] Hey folks- As discussed last month [1], the HDFS build hasn't been healthy recently. We're dedicating a bug bash to stabilize the build and address some longstanding issues with our unit tests. We rely on our CI infrastructure to keep the

[jira] [Created] (MAPREDUCE-7016) Avoid making separate RPC calls for FileStatus and block locations in FileInputFormat

Chris Douglas created MAPREDUCE-7016: Summary: Avoid making separate RPC calls for FileStatus and block locations in FileInputFormat Key: MAPREDUCE-7016 URL: https://issues.apache.org/jira/browse/MAPREDUCE

[jira] [Created] (MAPREDUCE-7013) Tests of internal logic should not use the local FS as scratch space

Chris Douglas created MAPREDUCE-7013: Summary: Tests of internal logic should not use the local FS as scratch space Key: MAPREDUCE-7013 URL: https://issues.apache.org/jira/browse/MAPREDUCE-7013

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

+1 (binding) Verified source tarball. Checksum and signature match, built from source, ran some unit tests. Skimmed NOTICE/LICENSE. -C On Mon, Nov 13, 2017 at 4:10 PM, Arun Suresh wrote: > Hi Folks, > > Apache Hadoop 2.9.0 is the first release of Hadoop 2.9 line and will be

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

The labor required for these release formalisms is exceeding their value. Our minor releases have more bugs than our patch releases (we hope), but every consumer should understand how software versioning works. Every device I own has bugs on major OS updates. That doesn't imply that every minor

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

Sean/Junping- Ignoring the epistemology, it's a problem. Let's figure out what's causing memory to balloon and then we can work out the appropriate remedy. Is this reproducible outside the CI environment? To Junping's point, would YETUS-561 provide more detailed information to aid debugging? -C

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

+1 (binding) Looked through the src distribution. Checksum, signatures match, ran some of the unit tests. Also checked the site docs; thanks for updating the Docker container security docs. Thanks, Junping. -C On Thu, Oct 19, 2017 at 5:42 PM, Junping Du wrote: > Hi folks,

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

d that it shouldn't be enabled in secure environments. How are users supposed to make this determination without it? > Vote still continue until a real blocker comes. Soright. I remain -1. -C > ________ > From: Chris Douglas <cdoug...@apache.org> > Sent: M

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

-1 (binding) I don't think we should release this without YARN-6622. Since this doesn't happen often: a -1 in this case is NOT a veto. Releases are approved by majority vote of the PMC. -C On Mon, Sep 11, 2017 at 11:45 AM, Junping Du wrote: > Thanks Mikols for notifying

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

+1 (binding) Looked through the src tarball. Checksum and signature match, skimmed NOTICE/LICENSE, ran some unit tests. -C On Sat, Jul 29, 2017 at 4:29 PM, Konstantin Shvachko wrote: > Hi everybody, > > Here is the next release of Apache Hadoop 2.7 line. The previous

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

gt; On Mon, Jul 31, 2017 at 3:56 PM Chris Douglas <cdoug...@apache.org> wrote: > >> On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko >> <shv.had...@gmail.com> wrote: >> > For the packaging, here is the exact phrasing from the sited >> release-policy &

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

On Mon, Jul 31, 2017 at 3:02 PM, Konstantin Shvachko wrote: > For the packaging, here is the exact phrasing from the sited release-policy > document relevant to binaries: > "As a convenience to users that might not have the appropriate tools to > build a compiled version of

[jira] [Reopened] (MAPREDUCE-6433) launchTime may be negative

[ https://issues.apache.org/jira/browse/MAPREDUCE-6433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas reopened MAPREDUCE-6433: -- > launchTime may be negative > -- > >

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

On Wed, Mar 29, 2017 at 4:59 PM, Stack wrote: >> The former; an intermediate handler decoding, [modifying,] and >> encoding the record without losing unknown fields. >> > > I did not try this. Did you? Otherwise I can. Yeah, I did. Same format. -C >> This looks fine. -C >> >>

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

On Wed, Mar 29, 2017 at 1:13 PM, Stack wrote: > Is the below evidence enough that pb3 in proto2 syntax mode does not drop > 'unknown' fields? (Maybe you want evidence that java tooling behaves the > same?) I reproduced your example with the Java tooling, including changing some

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

On Tue, Mar 28, 2017 at 4:18 PM, Andrew Wang wrote: > Unfortunately, it sounds like these are intrinsic differences with PB3. That's too bad... but possibly not fatal: most of the data we proxy through client code is, if not opaque, it's at least immutable (particularly

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

On Tue, Mar 28, 2017 at 3:04 PM, Andrew Wang wrote: > There's no mention of the convenient "Embedded messages are compatible with >> bytes if the bytes contain an encoded version of the message" semantics in >> proto3. > > > I checked the proto3 guide, and I think this

Re: Understanding task commit/abort protocol

, Steve Loughran <ste...@hortonworks.com> wrote: > >> On 3 Feb 2017, at 20:02, Chris Douglas <chris.doug...@gmail.com> wrote: >> >> It's been a long time, but IIRC this isn't going to be invoked. The AM >> will never set the preempt flag in the umbilica

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

On Wed, Jan 25, 2017 at 11:42 AM, Andrew Wang wrote: > Chris and Karthik, could you clarify the contingency of your votes? Is > fixing just the release notes sufficient? My +1 was not contingent on any changes. The release is fine as-is. Fixing any subset of the

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

On Mon, Jan 23, 2017 at 9:32 PM, Allen Wittenauer wrote: > The problem here is that there is a 'license' directory and a file called > 'LICENSE'. If this gets extracted by jar via jar xf, it will fail. unzip > can be made to extract it via an option like -o. To

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

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 on the VOTE, IMO. What's the issue with the minicluster jar [1]? I tried to reproduce, but

Re: [VOTE] Release cadence and EOL

On Fri, Jan 20, 2017 at 2:50 PM, Sangjin Lee wrote: > The security patch for the 2.6.x line is a case in point. Without any > guideline, we would start with "What should we do for 2.6.x? Should we > continue to patch it?" With this guideline, the baseline is already "it's > been

Re: [VOTE] Release cadence and EOL

Sorry, I'd missed the end of the EOL discussion thread. As several people have pointed out, this is unenforceable. The release dates on the front page are a decent signal for liveness... do we need something more formal? All these hypothetical situations would be decided with more context. The

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

+1 Verified checksum and signature. Unpacked the jar, started single-node HDFS cluster, did some cursory checks. Read through the commit log from 2.6.4; particularly happy to see HADOOP-12893. -C On Tue, Sep 27, 2016 at 1:28 PM, Sangjin Lee wrote: > Hi folks, > > I have

Re: [VOTE] Merge HADOOP-13341

+1 (also on JIRA) -C On Wed, Sep 7, 2016 at 6:44 AM, Allen Wittenauer wrote: > > I’d like to call for a vote to run for 5 days (ending Mon 12, 2016 > at 7AM PT) to merge the HADOOP-13341 feature branch into trunk. This branch > was developed exclusively by

Re: [DISCUSS] Release numbering semantics with concurrent (>2) releases [Was Setting JIRA fix versions for 3.0.0 releases]

> I'm certainly open to alternate proposals for versioning and fix versions, > but to reiterate, I like this versioning since it imitates other enterprise > software. RHEL has versions like 6.2 Beta 2 and 7.0 Beta, so versions like > 3.0.0-alpha1 will be immediately familiar to end users.

Re: Why there are so many revert operations on trunk?

Reading through HDFS-9924, a request for a design doc- and a -1 on committing to trunk- was raised in mid-May, but commits to trunk continued. Why is that? Shouldn't this have paused while the details were discussed? Branching is neutral to the pace of feature development, but consensus on the

Re: Looking to a Hadoop 3 release

If we're not starting branch-3/trunk, what would distinguish it from trunk/trunk-incompat? Is it the same mechanism with different labels? That may be a reasonable strategy when we create branch-3, as a release branch for beta. Releasing 3.x from trunk will help us figure out which

Re: [DISCUSS] Looking to a 2.8.0 release

With two active sustaining branches (2.6, 2.7), what would you think of releasing trunk as 3.x instead of pushing 2.8? There are many new features (EC, Y1197, etc.), and trunk could be the source of several alpha/beta releases before we fork the 3.x line. -C On Sat, Sep 26, 2015 at 12:49 PM,

Re: Looking to a Hadoop 3 release

On Fri, Mar 6, 2015 at 4:32 PM, Vinod Kumar Vavilapalli vino...@hortonworks.com wrote: I'd encourage everyone to post their wish list on the Roadmap wiki that *warrants* making incompatible changes forcing us to go 3.x. This is a useful exercise, but not a prerequisite to releasing 3.0.0 as an

Re: Looking to a Hadoop 3 release

On Mon, Mar 2, 2015 at 11:04 PM, Konstantin Shvachko shv.had...@gmail.com wrote: 2. If Hadoop 3 and 2.x are meant to exist together, we run a risk to manifest split-brain behavior again, as we had with hadoop-1, hadoop-2 and other versions. If that somehow beneficial for commercial vendors,

Re: [VOTE] Merge branch MAPREDUCE-2841 to trunk

+1 The change to the existing code is very limited and the perf is impressive. -C On Fri, Sep 5, 2014 at 4:58 PM, Todd Lipcon t...@apache.org wrote: Hi all, As I've reported recently [1], work on the MAPREDUCE-2841 branch has progressed well and the development team working on it feels that

Re: [VOTE] Migration from subversion to git for version control

+1 -C On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla ka...@cloudera.com wrote: I have put together this proposal based on recent discussion on this topic. Please vote on the proposal. The vote runs for 7 days. 1. Migrate from subversion to git for version control. 2. Force-push to

Re: [VOTE] Change by-laws on release votes: 5 days instead of 7

+1 -C On Tue, Jun 24, 2014 at 1:53 AM, Arun C Murthy a...@hortonworks.com wrote: Folks, As discussed, I'd like to call a vote on changing our by-laws to change release votes from 7 days to 5. I've attached the change to by-laws I'm proposing. Please vote, the vote will the usual

Re: [DISCUSS] sort improvement

The sort implementation is pluggable (see MAPREDUCE-2454, MAPREDUCE-4049), so please feel free to fork and improve it. Selecting a sort implementation based on job configuration (e.g., BinaryComparable keys) would allow for much more efficient and specialized implementations. -C On Thu, Mar 20,

Re: [VOTE] Release Apache Hadoop 2.3.0

+1 (binding) Verified checksum, signature. Built from src, poked at single-node cluster, ran some unit tests. -C On Tue, Feb 11, 2014 at 6:49 AM, Arun C Murthy a...@hortonworks.com wrote: Folks, I've created a release candidate (rc0) for hadoop-2.3.0 that I would like to get released. The

Re: [VOTE] Release Apache Hadoop 2.2.0

+1 Verified checksum and signature, built tarball, ran some unit tests. -C On Mon, Oct 7, 2013 at 12:00 AM, Arun C Murthy a...@hortonworks.com wrote: Folks, I've created a release candidate (rc0) for hadoop-2.2.0 that I would like to get released - this release fixes a small number of bugs

Re: [VOTE] Release Apache Hadoop 2.0.5-alpha (rc2)

+1 Checksum and signature match, ran some unit tests, checked diff against 2.0.4-alpha. Thanks for seeing this through, Cos. -C On Mon, Jun 3, 2013 at 1:13 PM, Alejandro Abdelnur t...@cloudera.com wrote: +1 RC2. Verified MD5 signature, checked CHANGES.txt files, built, configured pseudo

Re: [VOTE] Release Apache Hadoop 0.23.8

+1 Checksum and signature match, ran some tests. -C On Mon, Jun 3, 2013 at 1:19 PM, Sandy Ryza sandy.r...@cloudera.com wrote: +1 (non-binding). Did a full build from source and ran a few sample jobs on a pseudo-distributed cluster. -Sandy On Mon, Jun 3, 2013 at 11:29 AM, Kihwal Lee

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

On Thu, May 30, 2013 at 10:57 AM, Arun C Murthy a...@hortonworks.com wrote: Why not include MAPREDUCE-4211 as well rather than create one release per patch? From Cos's description, it sounded like these were backports of fixes to help Sqoop2 and fix some build issues. If it's not just to fixup

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

at 01:48PM, Chris Douglas wrote: On Thu, May 30, 2013 at 10:57 AM, Arun C Murthy a...@hortonworks.com wrote: Why not include MAPREDUCE-4211 as well rather than create one release per patch? From Cos's description, it sounded like these were backports of fixes to help Sqoop2 and fix some

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

be happy to learn my caution is unnecessary. -C On Thu, May 30, 2013 at 01:48PM, Chris Douglas wrote: On Thu, May 30, 2013 at 10:57 AM, Arun C Murthy a...@hortonworks.com wrote: Why not include MAPREDUCE-4211 as well rather than create one release per patch? From Cos's description

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

limit the vote thread to the merits of the release then? Happily. That sound like adding an insult to injury, if my forth-language skills do not mislead me. They do mislead you, or I've expressed the point imprecisely. We can take this offline. -C On Thu, May 30, 2013 at 01:48PM, Chris Douglas

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

+1 Checksum and signature match, ran some unit tests, verified w/ a diff of release-2.0.4-alpha that the release contains MAPREDUCE-5240 and HADOOP-9407, plus some fixups to the release notes. -C On Fri, May 24, 2013 at 8:48 PM, Konstantin Boudnik c...@apache.org wrote: All, I have created a

Re: Heads up - 2.0.5-beta

On Wed, May 1, 2013 at 6:24 PM, Arun C Murthy a...@hortonworks.com wrote: Having a strict policy leads to all sorts of further dialogues and issues we could do well without. +1 Can anyone remember why we vote on release plans? -C

Re: Heads up - 2.0.5-beta

On Thu, May 2, 2013 at 2:11 AM, Konstantin Shvachko shv.had...@gmail.com wrote: On Thu, May 2, 2013 at 12:07 AM, Chris Douglas cdoug...@apache.org wrote: Can anyone remember why we vote on release plans? -C To vote on features to include in the release. Since most features are developed

[jira] [Created] (MAPREDUCE-5194) Heed interrupts during Fetcher shutdown

Chris Douglas created MAPREDUCE-5194: Summary: Heed interrupts during Fetcher shutdown Key: MAPREDUCE-5194 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5194 Project: Hadoop Map/Reduce

[jira] [Created] (MAPREDUCE-5192) Separate TCE resolution from fetch

Chris Douglas created MAPREDUCE-5192: Summary: Separate TCE resolution from fetch Key: MAPREDUCE-5192 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5192 Project: Hadoop Map/Reduce

Re: [VOTE] Release Apache Hadoop 0.23.7

+1 Verified checksums and signatures, ran some tests, built the tarball. -C On Thu, Apr 11, 2013 at 12:55 PM, Thomas Graves tgra...@yahoo-inc.com wrote: I've created a release candidate (RC0) for hadoop-0.23.7 that I would like to release. This release is a sustaining release with several

Re: [VOTE] Release Apache Hadoop 2.0.4-alpha

+1 Verified checksum, signatures. Ran some tests, built the package. -C On Fri, Apr 12, 2013 at 2:56 PM, Arun C Murthy a...@hortonworks.com wrote: Folks, I've created a release candidate (RC2) for hadoop-2.0.4-alpha that I would like to release. The RC is available at:

Re: [Vote] Merge branch-trunk-win to trunk

Konstantin- There's no debate on the necessity of CI and related infrastructure to support the platform well. Suresh outlined the support to effect this here: http://s.apache.org/s1 Is the commitment to establish this infrastructure after the merge sufficient? -C On Fri, Mar 1, 2013 at 12:18

Re: [Vote] Merge branch-trunk-win to trunk

On Fri, Mar 1, 2013 at 1:57 PM, Konstantin Shvachko shv.had...@gmail.com wrote: Commitment is a good thing. I think the two builds that I proposed are a prerequisite for Win support. If we commit windows patch people will start breaking it the next day. Which we wont know without the nightly

[jira] [Created] (MAPREDUCE-5032) MapTask.MapOutputBuffer contains arithmetic overflows

Chris Douglas created MAPREDUCE-5032: Summary: MapTask.MapOutputBuffer contains arithmetic overflows Key: MAPREDUCE-5032 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5032 Project: Hadoop

Re: Yarn NodeManager services

On Tue, Oct 11, 2011 at 2:05 PM, milind.bhandar...@emc.com wrote: As part of MPI implementation in Yarn (aka Hamster), I was looking at refactoring some of the functionality into node manager services, so that it can be reused by other frameworks too. (Based on the discussion with some folks

Re: [VOTE] Merge MR-279 to trunk.

+1 -C On Tue, Aug 16, 2011 at 2:14 PM, Mahadev Konar maha...@hortonworks.com wrote: Hi all,  We are excited to let you know that we have MR-279 ready to be merged to trunk. I have uploaded necessary details on https://issues.apache.org/jira/browse/MAPREDUCE-279.  Please take a look and

[jira] [Resolved] (MAPREDUCE-2535) JobClient creates a RunningJob with null status and profile

[ https://issues.apache.org/jira/browse/MAPREDUCE-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas resolved MAPREDUCE-2535. -- Resolution: Fixed Committed the follow-up. Thanks for the quick fix. JobClient

[jira] [Reopened] (MAPREDUCE-2470) Receiving NPE occasionally on RunningJob.getCounters() call

[ https://issues.apache.org/jira/browse/MAPREDUCE-2470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas reopened MAPREDUCE-2470: -- Reverted while FI breakage is investigated Receiving NPE occasionally

[jira] [Resolved] (MAPREDUCE-2520) InputSampler.RandomSampler only accepts Text keys

[ https://issues.apache.org/jira/browse/MAPREDUCE-2520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas resolved MAPREDUCE-2520. -- Resolution: Invalid I see. This doesn't appear to be a bug in Hadoop, so I'm going

[jira] [Resolved] (MAPREDUCE-2468) MR-279: Metrics for shuffle

[ https://issues.apache.org/jira/browse/MAPREDUCE-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas resolved MAPREDUCE-2468. -- Resolution: Fixed Fix Version/s: (was: 0.23.0) Hadoop Flags

[jira] [Resolved] (MAPREDUCE-2411) When you submit a job to a queue with no ACLs you get an inscrutible NPE

[ https://issues.apache.org/jira/browse/MAPREDUCE-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas resolved MAPREDUCE-2411. -- Resolution: Fixed Assignee: Dick King Hadoop Flags: [Reviewed] I

[jira] Resolved: (MAPREDUCE-1401) [Gridmix] Add a load generating factory

[ https://issues.apache.org/jira/browse/MAPREDUCE-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas resolved MAPREDUCE-1401. -- Resolution: Duplicate Resolved in MAPREDUCE-1840 [Gridmix] Add a load generating

[jira] Resolved: (MAPREDUCE-1376) Support for varied user submission in Gridmix

[ https://issues.apache.org/jira/browse/MAPREDUCE-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas resolved MAPREDUCE-1376. -- Hadoop Flags: [Reviewed] Fix Version/s: 0.22.0 Resolution: Fixed Fixed

[jira] Resolved: (MAPREDUCE-1711) Gridmix should provide an option to submit jobs to the same queues as specified in the trace.

[ https://issues.apache.org/jira/browse/MAPREDUCE-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas resolved MAPREDUCE-1711. -- Hadoop Flags: [Reviewed] Fix Version/s: 0.22.0 Resolution: Fixed Fixed

[jira] Resolved: (MAPREDUCE-1594) Support for Sleep Jobs in gridmix

[ https://issues.apache.org/jira/browse/MAPREDUCE-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas resolved MAPREDUCE-1594. -- Hadoop Flags: [Reviewed] Assignee: rahul k singh Fix Version/s

[jira] Resolved: (MAPREDUCE-1844) Tests failing with java.lang.NoClassDefFoundError

[ https://issues.apache.org/jira/browse/MAPREDUCE-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas resolved MAPREDUCE-1844. -- Resolution: Fixed Fixed by HDFS-1193 Tests failing

New Common/MapReduce committer: Amareshwari Sriramadasu

The Hadoop PMC has voted to make Amareshwari Sriramadasu a committer on the Common and MapReduce subprojects. Congratulations Amareshwari! Thanks for all your past and continued work on Hadoop. -C

Contributor Meeting Minutes 05/28/2010

This month, the MapReduce + HDFS contributor meeting was held at Cloudera Headquarters. Announcements for contributor meetings are here: http://www.meetup.com/Hadoop-Contributors/ Minutes follow. No decisions were made at this meeting, but the following issues were discussed and may presage

[jira] Created: (MAPREDUCE-1683) Remove JNI calls from ClusterStatus cstr

Affects Versions: 0.20.2 Reporter: Chris Douglas The {{ClusterStatus}} constructor makes two JNI calls to the {{Runtime}} to fetch memory information. {{ClusterStatus}} instances are often created inside the {{JobTracker}} to obtain other, unrelated metrics (sometimes from

[jira] Created: (MAPREDUCE-1622) Include slf4j dependencies in binary tarball

Reporter: Chris Douglas Priority: Minor Fix For: 0.22.0 After MAPREDUCE-1556 and HADOOP-6486, starting \*Trackers from a binary tarball produces the following warning: {noformat} SLF4J: Failed to load class org.slf4j.impl.StaticLoggerBinder. SLF4J: See http

[jira] Resolved: (MAPREDUCE-1571) OutOfMemoryError during shuffle

[ https://issues.apache.org/jira/browse/MAPREDUCE-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas resolved MAPREDUCE-1571. -- Resolution: Duplicate This is a duplicate of MAPREDUCE-1182

[jira] Created: (MAPREDUCE-1551) TestMiniMRLocalFS fails

Reporter: Chris Douglas {{TestMiniMRLocalFS}} fails consistently on trunk: {noformat} Testcase: testWithLocal took 38.957 sec Caused an ERROR File QuasiMonteCarlo_TMP_3_141592654/out/reduce-out does not exist. java.io.FileNotFoundException: File QuasiMonteCarlo_TMP_3_141592654/out/reduce-out

[jira] Resolved: (MAPREDUCE-623) Resolve javac warnings in mapred

[ https://issues.apache.org/jira/browse/MAPREDUCE-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas resolved MAPREDUCE-623. - Resolution: Fixed Fix Version/s: (was: 0.21.0) 0.20.2 I

[jira] Reopened: (MAPREDUCE-623) Resolve javac warnings in mapred

[ https://issues.apache.org/jira/browse/MAPREDUCE-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas reopened MAPREDUCE-623: - These changes should also be applied to 0.20 Resolve javac warnings in mapred

[jira] Reopened: (MAPREDUCE-433) TestReduceFetch failed.

[ https://issues.apache.org/jira/browse/MAPREDUCE-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas reopened MAPREDUCE-433: - TestReduceFetch failed. --- Key: MAPREDUCE-433

[jira] Resolved: (MAPREDUCE-433) TestReduceFetch failed.

[ https://issues.apache.org/jira/browse/MAPREDUCE-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas resolved MAPREDUCE-433. - Resolution: Fixed Fix Version/s: (was: 0.21.0) 0.20.2

[jira] Created: (MAPREDUCE-1405) unchecked cast warnings in trunk

unchecked cast warnings in trunk Key: MAPREDUCE-1405 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1405 Project: Hadoop Map/Reduce Issue Type: Bug Reporter: Chris Douglas

[jira] Created: (MAPREDUCE-1406) JobContext.MAP_COMBINE_MIN_SPILLS is misspelled

: 0.21.0 Reporter: Chris Douglas Priority: Trivial Attachments: M1406-0.patch {{JobContext.MAP_COMBINE_MIN_SPILLS}} is misspelled as {{JobContext.MAP_COMBINE_MIN_SPISS}} -- This message is automatically generated by JIRA. - You can reply to this email to add

[jira] Created: (MAPREDUCE-1401) [Gridmix] Add a load generating factory

/gridmix Reporter: Chris Douglas To replace previous Gridmix benchmarks (HADOOP-2369 , HADOOP-3770), it must be possible to put a sustained, saturating load on a cluster. While tools for manipulating traces (MAPREDUCE-1295) allow one to produce lighter or heavier load than observed

[jira] Created: (MAPREDUCE-1402) Remove src/benchmarks

Remove src/benchmarks - Key: MAPREDUCE-1402 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1402 Project: Hadoop Map/Reduce Issue Type: Task Components: benchmarks Reporter: Chris Douglas

[jira] Reopened: (MAPREDUCE-433) TestReduceFetch failed.

[ https://issues.apache.org/jira/browse/MAPREDUCE-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas reopened MAPREDUCE-433: - Per MAPREDUCE-1172, this needs to be ported to 0.20 TestReduceFetch failed

[jira] Created: (MAPREDUCE-1384) Rumen should return UGI information for users rather than String

Type: Improvement Reporter: Chris Douglas It would be cleaner for downstream tools if Rumen were to return the {{UserGroupInformation}} about users in the trace- including groups- instead of the username only -- This message is automatically generated by JIRA. - You can reply

[jira] Created: (MAPREDUCE-1376) Support for varied user submission in Gridmix

Components: contrib/gridmix Reporter: Chris Douglas Gridmix currently submits all synthetic jobs as the client user. It should be possible to map users in the trace to a set of users appropriate for the target cluster. -- This message is automatically generated by JIRA. - You can reply

[jira] Created: (MAPREDUCE-1324) Make MapTask.MapOutputBuffer a standalone class

Components: task Reporter: Chris Douglas Assignee: Chris Douglas Priority: Minor {{MapTask.MapOutputBuffer}} has few dependencies on its outer class, but is more than half its total length. It should be factored out into a separate class. -- This message

[jira] Resolved: (MAPREDUCE-1190) Add package.html to pi and pi.math packages.

[ https://issues.apache.org/jira/browse/MAPREDUCE-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas resolved MAPREDUCE-1190. -- Resolution: Fixed Fix Version/s: 0.22.0 Hadoop Flags: [Reviewed] I

[jira] Reopened: (MAPREDUCE-972) distcp can timeout during rename operation to s3

[ https://issues.apache.org/jira/browse/MAPREDUCE-972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas reopened MAPREDUCE-972: - distcp can timeout during rename operation to s3

[jira] Resolved: (MAPREDUCE-972) distcp can timeout during rename operation to s3

[ https://issues.apache.org/jira/browse/MAPREDUCE-972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas resolved MAPREDUCE-972. - Resolution: Fixed distcp can timeout during rename operation to s3

[jira] Created: (MAPREDUCE-1147) Map output records counter missing for map-only jobs in new API

Type: Bug Affects Versions: 0.20.1, 0.21.0 Reporter: Chris Douglas Priority: Blocker Fix For: 0.20.2 In the new API, the counter for map output records is not incremented for map-only jobs -- This message is automatically generated by JIRA. - You can

[jira] Reopened: (MAPREDUCE-1109) ConcurrentModificationException in jobtracker.jsp

[ https://issues.apache.org/jira/browse/MAPREDUCE-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas reopened MAPREDUCE-1109: -- This still exists in 0.20, right? Sorry, I only mentioned MAPREDUCE-679 because

[jira] Resolved: (MAPREDUCE-819) DistCP Guide - updates

[ https://issues.apache.org/jira/browse/MAPREDUCE-819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas resolved MAPREDUCE-819. - Resolution: Fixed This was committed. Thanks, Corinne! DistCP Guide - updates

[jira] Created: (MAPREDUCE-1063) Document Gridmix benchmark

Document Gridmix benchmark -- Key: MAPREDUCE-1063 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1063 Project: Hadoop Map/Reduce Issue Type: Task Components: benchmarks Reporter: Chris

[jira] Created: (MAPREDUCE-1061) Gridmix unit test should validate input/output bytes

Versions: 0.21.0 Reporter: Chris Douglas Fix For: 0.21.0 TestGridmixSubmission currently verifies only that the correct number of jobs have been run. The test should validate the I/O parameters it claims to satisfy. -- This message is automatically generated by JIRA

  1   2   >