The git repository seems to have stopped syncing the svn repository.
The most recent commit was for svn revision 1300392, and that was almost
24 hours ago. Does something need to be kicked to get it syncing again?
Jason
Are there plans to setup the regular Jenkins builds for branch-2? I
noticed branch-2 had a build failure recently, but there wasn't a
corresponding failure message sent to the dev list.
Jasonn
+1 (non-binding)
- Verified checksums and signatures on src and binary tarballs
- Built from source
- Deployed pseudo-distributed cluster and ran some example jobs
Jason
On 02/06/2013 09:59 PM, Arun C Murthy wrote:
Folks,
I've created a release candidate (rc0) for hadoop-2.0.3-alpha that I wo
+1 (binding)
- Verified signatures and checksums
- Installed single-node cluster from binary tarball and ran sample jobs
- Built from source, installed single-node cluster from resulting
binaries, and ran sample jobs
Jason
On 04/11/2013 02:55 PM, Thomas Graves wrote:
I've created a release c
+1 (binding)
- verified signatures and checksums
- installed single-node cluster from binaries and ran sample jobs
- built and installed single-node cluster from source and ran sample jobs
Jason
On 04/12/2013 04:56 PM, Arun C Murthy wrote:
Folks,
I've created a release candidate (RC2) for had
Matt, would you consider adding HADOOP-9504 to the release? Some groups
using HBase have been bitten by this bug and would like to see it in a
1.x release.
Jason
On 05/10/2013 11:44 AM, Matt Foley wrote:
Hi all,
just a reminder this vote is underway and will close Monday 11:30am.
Please revi
on release.
If I commit to doing 1.2.1 in 3 to 4 weeks, including this HADOOP-9504, would
that be acceptable to you?
Regards,
--Matt
On Fri, May 10, 2013 at 6:35 PM, Jason Lowe
mailto:jl...@yahoo-inc.com>> wrote:
Matt, would you consider adding HADOOP-9504 to the release? Some groups using
+1
On 05/17/2013 04:10 PM, Thomas Graves wrote:
Hello all,
We've had a few critical issues come up in 0.23.7 that I think warrants a
0.23.8 release. The main one is MAPREDUCE-5211. There are a couple of
other issues that I want finished up and get in before we spin it. Those
include HDFS-3875
+1
Jason
On 05/21/2013 09:03 PM, Matt Foley wrote:
This was previously discussed in the thread "[PROPOSAL] change in bylaws to
remove Release Plan vote". 13 people explicitly cast "+1"s in that thread.
Absent objection I will count those as votes without requiring them to
(re-)respond to thi
+1
- Verified signatures and checksums
- Verified MAPREDUCE-5211 was present in CHANGES.txt and source
- Built from source, deployed single-node cluster, ran example jobs
Jason
On 05/28/2013 11:00 AM, Thomas Graves wrote:
I've created a release candidate (RC0) for hadoop-0.23.8 that I would li
-1 (binding)
Ran into public localization issues and filed YARN-4354. We need that resolved
before the release is ready. We will either need a timely fix or may have to
revert YARN-2902 to unblock the release if my root-cause analysis is correct.
I'll dig into this more today.
Jason
Fr
+1 (binding)
- Verified signatures and digests- Successfully built from source with native
code support- Deployed to a single-node cluster and ran some test jobs
Jason
From: Junping Du
To: Hadoop Common ; "hdfs-...@hadoop.apache.org"
; "mapreduce-...@hadoop.apache.org"
; "yarn-...@hadoo
+1 (binding)
- Verified signatures and digests- Spot checked CHANGES.txt files- Successfully
performed a native build from source- Deployed to a single node cluster and ran
sample jobs
We have been running with the fix for YARN-4354 on two of our clusters for some
time with no issues, so I feel
-1 (binding)
We have been running a release derived from 2.7 on some of our clusters, and we
recently hit a bug where an application making large container requests can
drastically slow down container allocations for other users in the same queue.
See YARN-4610 for details. Since
yarn.schedul
doop.apache.org; Jason Lowe
Cc: Hadoop Common ; "hdfs-...@hadoop.apache.org"
; "yarn-...@hadoop.apache.org"
Sent: Tuesday, January 19, 2016 5:25 PM
Subject: Re: [VOTE] Release Apache Hadoop 2.7.2 RC2
The JIRA YARN-4610 links YARN-3434 as the one causing the breakage, and
+1 (binding)
- verified signatures and digests- built native from source- deployed a
single-node cluster and ran some sample MapReduce jobs.
Jason
From: Junping Du
To: "hdfs-...@hadoop.apache.org" ;
"yarn-...@hadoop.apache.org" ;
"mapreduce-...@hadoop.apache.org" ;
"common-dev@hadoop.
Someone in our group recently discovered that Configuration parameters
marked final can still be set(). The final designation only seems to be
important when loading resources and is ignored when individual
properties are modified. The javadocs do call out loaded resources
explicitly, but the
I thought Arun intends for 2.2.0 to be created off of branch-2.1.0-beta
and not off of branch-2. As I understand it, only critical blockers
will be the delta between 2.1.0-beta and 2.2.0 and items checked into
branch-2 should be marked as fixed in 2.3.0.
Part of the confusion is that current
I committed MAPREDUCE-5358 to branch-2 but did not commit it to
branch-2.1-beta since it wasn't a blocker and Arun was in the middle of
cutting the release.
Arun, if you feel it's appropriate to put this in branch-2.1-beta feel
free to pull it in or let me know. Thanks!
Jason
On 07/03/2013
+1
- Verified checksums and signatures
- Booted single-node cluster from binary tarball and ran a few sample jobs
- Built source distribution, installed a single-node cluster and ran a
few sample jobs
Jason
On 07/01/2013 12:20 PM, Thomas Graves wrote:
I've created a release candidate (RC0) f
Given the lack of feedback, I'm guessing this is just a bug. Filed
HADOOP-9725.
On 07/02/2013 09:34 AM, Jason Lowe wrote:
Someone in our group recently discovered that Configuration parameters
marked final can still be set(). The final designation only seems to
be important when lo
+1 (binding)
- verified signatures and checksums
- built from source
- ran some simple jobs on a single-node cluster
On 08/15/2013 04:15 PM, Arun C Murthy wrote:
Folks,
I've created a release candidate (rc2) for hadoop-2.1.0-beta that I would like
to get released - this fixes the bugs we saw
+1 (binding)
- Verified signatures and checksums
- Built source
- Deployed single-node cluster and ran some test jobs
Jason
On 08/16/2013 12:29 AM, Konstantin Boudnik wrote:
All,
I have created a release candidate (rc1) for hadoop-2.0.6-alpha that I would
like to release.
This is a stabiliza
+1 (binding)
- Verified signatures and checksums
- Deployed binary tarball to a single-node cluster and successfully ran
sample jobs
- Built source, deployed to a single-node cluster and successfully ran
sample jobs
Jason
On 10/07/2013 02:00 AM, Arun C Murthy wrote:
Folks,
I've created a r
I don't think that OOM error below indicates it needs more heap space,
as it's complaining about the ability to create a new native thread.
That usually is caused by lack of available virtual address space or
hitting process ulimits.
What's most likely going on is the jenkins user is hitting
ly tracked
by MAPREDUCE-5481 <https://issues.apache.org/jira/browse/MAPREDUCE-5481>
and/or find a way to keep it from escaping during builds. There might
be another issue where SocketReader threads can prevent the JVM from
shutting down completely in some cases.
Jason
On 10/31/2013 08:1
I think a lot of confusion comes from the fact that the 2.x line is
starting to mature. Before this there wasn't such a big contention of
what went into patch vs. minor releases and often the lines were blurred
between the two. However now we have significant customers and products
starting t
+1 (binding)
- verified signatures and digests
- deployed binary tarball to a single-node cluster and ran some jobs
- built from source
- deployed source build to a single-node cluster and ran some jobs
Jason
On 12/03/2013 12:22 AM, Thomas Graves wrote:
Hey Everyone,
There have been lots of i
I just committed the addendum patch for HADOOP-9652 which should resolve
the performance issue.
Speaking of critical issues to fix for 2.3, I do wonder what to do with
all the Blocker/Criticals targeted for 2.4 (the old branch-2 HEAD
release) which apparently is now going to be 2.3 (the new br
Thanks, Arun. Are there plans to update the Fix Versions and
CHANGES.txt accordingly? There are a lot of JIRAs that are now going to
ship in 2.3.0 but the JIRA and CHANGES.txt says they're not fixed until
2.4.0.
Jason
On 01/27/2014 08:47 AM, Arun C Murthy wrote:
Done. I've re-created branc
The RM issue should be fixed by YARN-1600 which I just committed this
morning.
Jason
On 01/29/2014 10:33 AM, Steve Loughran wrote:
I'm just switching over to use the 2.4-SNAPSHOT in a secured pseudo-dist
cluster, and now the services are failing to come up because the web
principals haven't be
We should hold off commits until that's done, right?
On Mon, Jan 27, 2014 at 1:07 PM, Arun C Murthy wrote:
Yep, on it as we speak. :)
Arun
On Jan 27, 2014, at 12:36 PM, Jason Lowe wrote:
Thanks, Arun. Are there plans to update the Fix Versions and
CHANGES.txt accordingly? The
+1 (binding)
- Verified signatures and digests
- Built from source with native support
- Deployed a single-node cluster and ran some sample jobs
Jason
On 02/11/2014 08:49 AM, Arun C Murthy wrote:
Folks,
I've created a release candidate (rc0) for hadoop-2.3.0 that I would like to
get released
Here's my late +1, was just finishing up looking at the release.
- Verified signatures and digests
- Examined LICENSE file
- Installed binary distribution, ran some sample MapReduce jobs and
examined logs and job history
- Built from source
Jason
On 04/07/2014 03:04 PM, Arun C Murthy wrote:
+1 (binding)
Jason
On 06/24/2014 03:53 AM, Arun C Murthy 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 period of 7 days.
tha
+1 (binding)
- Verified signatures and digests
- Deployed binary tarball to a single-node cluster and ran some MR
example jobs
- Built from source, deployed to a single-node cluster and ran some MR
example jobs
Jason
On 06/19/2014 10:14 AM, Thomas Graves wrote:
Hey Everyone,
There have bee
+1
- Verified signatures and digests
- Built from source, installed on single-node cluster and ran some
sample jobs
Jason
On 06/21/2014 01:51 AM, Arun C Murthy wrote:
Folks,
I've created another release candidate (rc1) for hadoop-2.4.1 based on the
feedback that I would like to push out.
I think that's a reasonable proposal as long as we understand it changes
the burden from finding all the things that should be marked @Private to
finding all the things that should be marked @Public. As Tom Graves
pointed out in an earlier discussion about @LimitedPrivate, it may be
impossible
+1
Jason
On 08/08/2014 09:57 PM, Karthik Kambatla 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 be disabled on trunk and
+1 (binding)
- verified signatures and digests
- built from source
- deployed a single-node cluster
- ran some sample jobs
Jason
On 08/06/2014 03:59 PM, Karthik Kambatla wrote:
Hi folks,
I have put together a release candidate (rc2) for Hadoop 2.5.0.
The RC is available at: http://people.apa
+1 (binding)
- verified signatures and digests
- built from source
- examined CHANGES.txt for items fixed in 2.5.1
- deployed to a single-node cluster and ran some sample MR jobs
Jason
On 09/05/2014 07:18 PM, Karthik Kambatla wrote:
Hi folks,
I have put together a release candidate (RC0) for
Is it necessary to cut the branch so far ahead of the release? branch-3.0
is already a maintenance line for 3.0.x releases. Is there a known
feature/improvement planned to go into branch-3.0 that is not desirable for
the 3.0.1 release?
I have found in the past that branching so early leads to ma
I recently noticed some committers posting commits to branch-3 and marking
the JIRA as fixed in 3.0.1. I thought branch-3.0 was tracking 3.0.x
releases, including branch-3.0.1 as of now, so I am confused what branch-3
is for. The versions in the poms between branch-3 and branch-3.0 both say
they
O,we no need to have *branch-3* still trunk moves.Shall we remove as it
> make confuses.??
>
>
>
>
> Brahma Reddy Battula
>
> On Wed, Jan 17, 2018 at 9:41 PM, Jason Lowe
> wrote:
>
> > I recently noticed some committers posting commits to branch-3 and
>
own.
> -Eric
>
>
> From: Jason Lowe
> To: Hadoop Common ; ma...@cloudera.com
> Sent: Wednesday, January 17, 2018 12:42 PM
> Subject: Re: What's the difference between branch-3 and branch-3.0?
>
> This was created accidentally when HDFS-11847 was committed. As such we
CVE-2017-15713: Apache Hadoop MapReduce job history server vulnerability
Severity: Severe
Vendor: The Apache Software Foundation
Versions Affected:
Hadoop 0.23.0 to 0.23.11
Hadoop 2.0.0-alpha to 2.8.2
Hadoop 3.0.0-alpha to 3.0.0-beta1
Users affected: Users running the MapReduce job histor
Thanks for driving the release, Konstatin!
+1 (binding)
- Verified signatures and digests
- Completed a native build from source
- Deployed a single-node cluster
- Ran some sample jobs
Jason
On Mon, Apr 9, 2018 at 6:14 PM, Konstantin Shvachko
wrote:
> Hi everybody,
>
> This is the next dot rel
eappeared. Filed INFRA-16086 [1]. -C
>
> [1]: https://issues.apache.org/jira/browse/INFRA-16086
>
>
> On Wed, Jan 17, 2018 at 12:32 PM, Jason Lowe wrote:
>> I filed INFRA-15859 to have branch-3 deleted.
>>
>> Jason
>>
>> On Wed, Jan 17, 2018 at 1:23
Thanks for driving this release, Steve!
+1 (binding)
- Verified signatures and digests
- Successfully performed a native build from source
- Deployed a single-node cluster
- Ran some sample jobs and checked web UI and logs
Jason
On Wed, Jul 11, 2018 at 10:05 AM, Steve Loughran
wrote:
>
>
> H
Thanks for driving the release, Junping!
+1 (binding)
- Verified signatures and digests
- Successfully performed a native build from source
- Successfully deployed a single-node cluster with the timeline server
- Ran some sample jobs and examined the web UI and job logs
Jason
On Mon, Sep 10, 20
I am happy to announce that Oath will be hosting the next Hadoop
Contributors meetup on Tuesday, September 25th at Yahoo Building G, 589
Java Drive, Sunnyvale CA from 8:00AM to 6:00PM.
The agenda will look roughly as follows:
08:00AM - 08:30AM Arrival and Check-in
08:30AM - 12:00PM A series of br
Thanks for driving this release, Akira!
+1 (binding)
- Verified signatures and digests
- Successfully performed native build from source
- Deployed a single-node cluster and ran some sample jobs
Jason
On Tue, Nov 13, 2018 at 7:02 PM Akira Ajisaka wrote:
> Hi folks,
>
> I have put together a r
Thanks for driving this release, Sunil!
+1 (binding)
- Verified signatures and digests
- Successfully performed a native build
- Deployed a single-node cluster
- Ran some sample jobs
Jason
On Fri, Nov 23, 2018 at 6:07 AM Sunil G wrote:
> Hi folks,
>
>
>
> Thanks to all contributors who helped
+1 (binding)
- Verified signatures and digests- Built from source with native support-
Deployed a pseudo-distributed cluster- Ran some sample jobs
Jason
From: Vinod Kumar Vavilapalli
To: "common-dev@hadoop.apache.org" ;
hdfs-...@hadoop.apache.org; yarn-...@hadoop.apache.org;
"mapreduce-
Both sound like real problems to me, and I think it's appropriate to file JIRAs
to track them.
Jason
From: Andrew Wang
To: Karthik Kambatla
Cc: larry mccay ; Vinod Kumar Vavilapalli
; "common-dev@hadoop.apache.org"
; "hdfs-...@hadoop.apache.org"
; "yarn-...@hadoop.apache.org"
; "ma
Thanks for organizing this, Chris!
I don't believe HADOOP-13362 is needed since it's related to ContainerMetrics.
ContainerMetrics weren't added until 2.7 by YARN-2984.
YARN-4794 looks applicable to 2.6. The change drops right in except it has
JDK7-isms (multi-catch clause), so it needs a sligh
+1 (binding)
- Verified signatures and digests- Built from source with native support-
Deployed a pseudo-distributed cluster- Ran some sample jobs
Jason
From: Vinod Kumar Vavilapalli
To: "common-dev@hadoop.apache.org" ;
hdfs-...@hadoop.apache.org; yarn-...@hadoop.apache.org;
"mapreduce-
+1 (binding)
- Verified signatures and digests- Successfully built from source with native
support- Deployed a single-node cluster- Ran some sample jobs successfully
Jason
From: Vinod Kumar Vavilapalli
To: "common-dev@hadoop.apache.org" ;
hdfs-...@hadoop.apache.org; yarn-...@hadoop.apac
+1 (binding)
- Verified signatures and digests- Built native from source- Deployed to a
single-node cluster and ran some sample jobs
Jason
On Sunday, October 2, 2016 7:13 PM, Sangjin Lee wrote:
Hi folks,
I have pushed a new release candidate (R1) for the Apache Hadoop 2.6.5
release (t
At this point my preference would be to do the most expeditious thing to
release 2.8, whether that's sticking with the branch-2.8 we have today or
re-cutting it on branch-2. Doing a quick JIRA query, there's been almost 2,400
JIRAs resolved in 2.8.0 (1). For many of them, it's well-past time t
+1 (binding)
- Verfied signatures and digests- Performed a native build from the release
tag- Deployed to a single node cluster- Ran some sample jobs
Jason
On Friday, March 17, 2017 4:18 AM, Junping Du wrote:
Hi all,
With fix of HDFS-11431 get in, I've created a new release candida
I found at least one commit that was dropped, MAPREDUCE-6673. I was able to
cherry-pick the original commit hash since it was recorded in the commit email.
This begs the question of why we're allowing force pushes to trunk. I thought
we asked to have that disabled the last time trunk was accide
&focusedCommentId=15971643#comment-15971643
Jason
On Monday, April 17, 2017 3:05 PM, Sean Busbey wrote:
disallowing force pushes to trunk was done back in:
* August 2014: INFRA-8195
* February 2016: INFRA-11136
On Mon, Apr 17, 2017 at 11:18 AM, Jason Lowe
wrote:
> I found at le
I think we are OK to leave support for the zstd codec in the Hadoop code base.
I asked Chris Mattman for clarification, noting that the support for the zstd
codec requires the user to install the zstd headers and libraries and then
configure it to be included in the native Hadoop build. The Ha
+1 to base the 2.8.2 release off of the more recent activity on branch-2.8.
Because branch-2.8.2 was cut so long ago it is missing a lot of fixes that are
in branch-2.8. There also are a lot of JIRAs that claim they are fixed in
2.8.2 but are not in branch-2.8.2. Having the 2.8.2 release be b
Thanks for driving the 2.7.4 release!
+1 (binding)
- Verified signatures and digests- Successfully built from source including
native- Deployed to a single-node cluster and ran sample MapReduce jobs
Jason
On Saturday, July 29, 2017 6:29 PM, Konstantin Shvachko
wrote:
Hi everybody,
Her
+1 for Steve's and Chris's sentiments. Mass reformatting of existing code can
make maintaining anything released prior to the makeover very difficult.
Almost all of Apache Hadoop's users are not on trunk or branch-2, and I'm not
sure we want large refactoring patches going into stability lines
Andrew Wang wrote:
> This means I'll cut branch-3 and
> branch-3.0, and move trunk to 4.0.0 before these VOTEs end. This will open
> up development for Hadoop 3.1.0 and 4.0.0.
I can see a need for branch-3.0, but please do not create branch-3. Doing
so will relegate trunk back to the "patch pu
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 that
> it's not good enough?
It is a burden for that first, "this can't go anywhere else but 4.x"
change, but arguably that sho
Allen Wittenauer wrote:
> > On Aug 25, 2017, at 1:23 PM, Jason Lowe 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
rt.
>
> We paid close attention to ensure that once disabled Timeline Service v.2
> does not impact existing functionality when disabled (by default).
>
> Special thanks to a team of folks who worked hard and contributed towards
> this effort with patches, reviews and guidance: Roh
+1 (binding)
- Verified signatures and digests
- Performed a native build from source
- Deployed to a single-node cluster
- Ran some sample jobs
The CHANGES.md and RELEASENOTES.md both refer to release 2.8.0 instead of
2.8.2, and I do not see the list of JIRAs in CHANGES.md that have been
committ
both of them for 2.8.2 (for real this time!) and they look
correct. Again my apologies for the confusion.
Jason
On Mon, Oct 23, 2017 at 3:26 PM, Jason Lowe wrote:
> +1 (binding)
>
> - Verified signatures and digests
> - Performed a native build from source
> - Deployed to a sing
Thanks for putting this release together!
+1 (binding)
- Verified signatures and digests
- Successfully built from source including native
- Deployed to single-node cluster and ran some test jobs
Jason
On Mon, Nov 13, 2017 at 6:10 PM, Arun Suresh wrote:
> Hi Folks,
>
> Apache Hadoop 2.9.0 is
Is it possible to track the patch by JIRA attachment ID rather than assume
the most recent attachment is the right one? I thought the admin precommit
build was kicking off the project-specific precommit build with an
attachment ID argument so the project precommit can be consistent with the
admin
Thanks for driving this release, Junping!
+1 (binding)
- Verified signatures and digests
- Successfully performed native build from source
- Deployed a single-node cluster
- Ran some test jobs and examined the logs
Jason
On Tue, Dec 5, 2017 at 3:58 AM, Junping Du wrote:
> Hi all,
> I've
Thanks for driving the release, Konstantin!
+1 (binding)
- Verified signatures and digests
- Successfully performed a native build from source
- Deployed a single-node cluster
- Ran some sample jobs and checked the logs
Jason
On Thu, Dec 7, 2017 at 9:22 PM, Konstantin Shvachko
wrote:
> Hi ev
I just committed 2.6 blockes YARN-2846 and MAPREDUCE-6156 which should also be
in the 2.6.0 rc1 build.
Jason
From: Arun C Murthy
To: yarn-...@hadoop.apache.org
Cc: mapreduce-...@hadoop.apache.org; Ravi Prakash ;
"hdfs-...@hadoop.apache.org" ;
"common-dev@hadoop.apache.org"
Sent: Wedn
+1 (binding)
- verified signatures and digests- verified late-arriving fixes for YARN-2846
and MAPREDUCE-6156 were present
- built from source- deployed to a single-node cluster
- ran some sample MapReduce jobs
Jason
From: Arun C Murthy
To: "common-dev@hadoop.apache.org" ;
"hdfs-...@hado
I'd like to see a 2.7 release sooner than later. It has been almost 3 months
since Hadoop 2.6 was released, and there have already been 634 JIRAs committed
to 2.7. That's a lot of changes waiting for an official release.
https://issues.apache.org/jira/issues/?jql=project%20in%20%28hadoop%2Chdfs
I'm OK with a 3.0.0 release as long as we are minimizing the pain of
maintaining yet another release line and conscious of the incompatibilities
going into that release line.
For the former, I would really rather not see a branch-3 cut so soon. It's yet
another line onto which to cherry-pick, a
+1 (binding)
- Verified signatures and digests- Built from source with native support-
Deployed to a single-node cluster and ran sample jobs
Jason
From: Vinod Kumar Vavilapalli
To: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org;
yarn-...@hadoop.apache.org; mapreduce-...@hadoop.
+1 (binding)
- Verified signatures and digests
- Successfully performed a native build from source- Deployed a single-node
cluster- Ran sample MapReduce jobs
Jason
From: Vinod Kumar Vavilapalli
To: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org;
yarn-...@hadoop.apache.org; mapr
+1 (binding)
- Verified signatures and digests- Performed native build from source- Deployed
a single-node cluster and ran some test jobs
Jason
From: Sangjin Lee
To: "common-dev@hadoop.apache.org" ;
"yarn-...@hadoop.apache.org" ;
"hdfs-...@hadoop.apache.org" ;
"mapreduce-...@hadoop.apa
Jason Lowe created HADOOP-8495:
--
Summary: Update Netty to avoid leaking file descriptors during
shuffle
Key: HADOOP-8495
URL: https://issues.apache.org/jira/browse/HADOOP-8495
Project: Hadoop Common
Jason Lowe created HADOOP-8691:
--
Summary: FsShell can print "Found xxx items" unnecessarily often
Key: HADOOP-8691
URL: https://issues.apache.org/jira/browse/HADOOP-8691
Project: Had
Jason Lowe created HADOOP-8709:
--
Summary: globStatus changed behavior from 0.20/1.x
Key: HADOOP-8709
URL: https://issues.apache.org/jira/browse/HADOOP-8709
Project: Hadoop Common
Issue Type
Jason Lowe created HADOOP-8723:
--
Summary: Remove tests and tests-sources jars from classpath
Key: HADOOP-8723
URL: https://issues.apache.org/jira/browse/HADOOP-8723
Project: Hadoop Common
Issue
Jason Lowe created HADOOP-8735:
--
Summary: Missing support for dfs.umaskmode
Key: HADOOP-8735
URL: https://issues.apache.org/jira/browse/HADOOP-8735
Project: Hadoop Common
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HADOOP-8735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe resolved HADOOP-8735.
Resolution: Duplicate
> Missing support for dfs.umaskm
Jason Lowe created HADOOP-8942:
--
Summary: Thundering herd of RPCs with large responses leads to OOM
Key: HADOOP-8942
URL: https://issues.apache.org/jira/browse/HADOOP-8942
Project: Hadoop Common
Jason Lowe created HADOOP-8962:
--
Summary: RawLocalFileSystem.listStatus fails when a child filename
contains a colon
Key: HADOOP-8962
URL: https://issues.apache.org/jira/browse/HADOOP-8962
Project
Jason Lowe created HADOOP-8967:
--
Summary: Reported source for config property can be misleading
Key: HADOOP-8967
URL: https://issues.apache.org/jira/browse/HADOOP-8967
Project: Hadoop Common
Jason Lowe created HADOOP-9069:
--
Summary: FileSystem.get leads to stack overflow if default FS is
not configured with a scheme
Key: HADOOP-9069
URL: https://issues.apache.org/jira/browse/HADOOP-9069
Jason Lowe created HADOOP-9193:
--
Summary: hadoop script can inadvertently expand wildcard arguments
when delegating to hdfs script
Key: HADOOP-9193
URL: https://issues.apache.org/jira/browse/HADOOP-9193
Jason Lowe created HADOOP-9344:
--
Summary: Configuration.writeXml can warn about deprecated
properties user did not set
Key: HADOOP-9344
URL: https://issues.apache.org/jira/browse/HADOOP-9344
Project
Jason Lowe created HADOOP-9397:
--
Summary: Incremental dist tar build fails
Key: HADOOP-9397
URL: https://issues.apache.org/jira/browse/HADOOP-9397
Project: Hadoop Common
Issue Type: Bug
Jason Lowe created HADOOP-9404:
--
Summary: Reconcile dist-maketar.sh and dist-tar-stitching.sh
Key: HADOOP-9404
URL: https://issues.apache.org/jira/browse/HADOOP-9404
Project: Hadoop Common
Jason Lowe created HADOOP-9546:
--
Summary: "setsid exited with exit code" message on each hadoop
command
Key: HADOOP-9546
URL: https://issues.apache.org/jira/browse/HADOOP-9546
Project: Had
Jason Lowe created HADOOP-9583:
--
Summary: test-patch gives +1 despite build failure when running
tests
Key: HADOOP-9583
URL: https://issues.apache.org/jira/browse/HADOOP-9583
Project: Hadoop Common
1 - 100 of 171 matches
Mail list logo
