+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
+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
+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
+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
+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
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
+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)
+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
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
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:19 AM, Jason Lowe
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
+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
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
On Mon, Jan 27, 2014 at 1:31 PM, Sandy Ryza sandy.r...@cloudera.com wrote:
We should hold off commits until that's done, right?
On Mon, Jan 27, 2014 at 1:07 PM, Arun C Murthy a...@hortonworks.comwrote:
Yep, on it as we speak. :)
Arun
On Jan 27, 2014, at 12:36 PM, Jason Lowe jl...@yahoo
+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
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.
+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
+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.
+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
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 a...@hortonworks.com
To: yarn-...@hadoop.apache.org
Cc: mapreduce-...@hadoop.apache.org; Ravi Prakash ravi...@ymail.com;
hdfs-dev@hadoop.apache.org
+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 a...@hortonworks.com
To:
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,
+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 vino...@apache.org
To: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
yarn-...@hadoop.apache.org;
+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 vino...@apache.org
To: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
+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-...@hadoop.apache.org" ;
"yarn-...@hadoop.apache.org"
-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
+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-dev@hadoop.apache.org"
+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)
- 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-dev@hadoop.apache.org" ;
"yarn-...@hadoop.apache.org"
reduce-...@hadoop.apache.org; Jason Lowe <jl...@yahoo-inc.com>
Cc: Hadoop Common <common-...@hadoop.apache.org>; "hdfs-dev@hadoop.apache.org"
<hdfs-dev@hadoop.apache.org>; "yarn-...@hadoop.apache.org"
<yarn-...@hadoop.apache.org>
Sent: Tuesday, January 19
-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
+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-...@hadoop.apache.org" ;
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
+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-...@hadoop.apache.org" ;
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
;
+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-...@hadoop.apache.org"
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
+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
+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
=15971643#comment-15971643
Jason
On Monday, April 17, 2017 3:05 PM, Sean Busbey <bus...@cloudera.com> 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
<jl...@yahoo-inc.co
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:
+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
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
Allen Wittenauer wrote:
> > 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 hap
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
t;
> 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: Rohith Sharma
+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
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 <jl...@oath.com> wrote:
> +1 (binding)
>
> - Verified signatures and digests
> - Performed a native build from s
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
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:
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,
>
>
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
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,
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,
>
>
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
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
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
Affects Versions: 0.24.0
Reporter: Jason Lowe
Building the eclipse:eclipse target fails in the hadoop-hdfs-httpfs project
with this error:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-eclipse-plugin:2.8:eclipse (default-cli) on
project hadoop-hdfs-httpfs: Request
Reporter: Jason Lowe
Assignee: Jason Lowe
This is the HDFS portion of HADOOP-8005. HDFS no longer depends upon slf4j, so
removing it from the assembly will eliminate the HDFS-portion of the multiple
SLF4J warnings.
--
This message is automatically generated by JIRA.
If you think
Reporter: Jason Lowe
Priority: Blocker
Build fails when trying to build branch-2:
[ERROR]
/hadoop/src/branch-2/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java:[2741,32]
unreported exception java.io.IOException; must be caught
Jason Lowe created HDFS-3554:
Summary: TestRaidNode is failing
Key: HDFS-3554
URL: https://issues.apache.org/jira/browse/HDFS-3554
Project: Hadoop HDFS
Issue Type: Bug
Components
Jason Lowe created HDFS-3563:
Summary: Fix findbug warnings in raid
Key: HDFS-3563
URL: https://issues.apache.org/jira/browse/HDFS-3563
Project: Hadoop HDFS
Issue Type: Bug
Components
[
https://issues.apache.org/jira/browse/HDFS-3648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe resolved HDFS-3648.
--
Resolution: Duplicate
TestRaidNode.testDistRaid fails
Jason Lowe created HDFS-3831:
Summary: Failure to renew tokens due to test-sources left in
classpath
Key: HDFS-3831
URL: https://issues.apache.org/jira/browse/HDFS-3831
Project: Hadoop HDFS
Jason Lowe created HDFS-4328:
Summary: TestLargeBlock#testLargeBlockSize is timing out
Key: HDFS-4328
URL: https://issues.apache.org/jira/browse/HDFS-4328
Project: Hadoop HDFS
Issue Type: Bug
Jason Lowe created HDFS-4426:
Summary: Secondary namenode shuts down immediately after startup
Key: HDFS-4426
URL: https://issues.apache.org/jira/browse/HDFS-4426
Project: Hadoop HDFS
Issue Type
Jason Lowe created HDFS-4427:
Summary: start-dfs.sh generates malformed ssh command when not
running with native libs
Key: HDFS-4427
URL: https://issues.apache.org/jira/browse/HDFS-4427
Project: Hadoop
Jason Lowe created HDFS-6021:
Summary: NPE in FSImageFormatProtobuf upgrading from layout -52 to
-53
Key: HDFS-6021
URL: https://issues.apache.org/jira/browse/HDFS-6021
Project: Hadoop HDFS
[
https://issues.apache.org/jira/browse/HDFS-6021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe resolved HDFS-6021.
--
Resolution: Duplicate
Resolving as a dup of HDFS-5988 since that seems like the most likely culprit
Jason Lowe created HDFS-6421:
Summary: RHEL4 fails to compile vecsum.c
Key: HDFS-6421
URL: https://issues.apache.org/jira/browse/HDFS-6421
Project: Hadoop HDFS
Issue Type: Bug
Jason Lowe created HDFS-6840:
Summary: Clients are always sent to the same datanode when read is
off rack
Key: HDFS-6840
URL: https://issues.apache.org/jira/browse/HDFS-6840
Project: Hadoop HDFS
[
https://issues.apache.org/jira/browse/HDFS-6907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe resolved HDFS-6907.
--
Resolution: Duplicate
Dup of HDFS-6905.
Source files missing license headers
Jason Lowe created HDFS-7199:
Summary: DFSOutputStream can silently drop data if DataStreamer
crashes with a non-I/O exception
Key: HDFS-7199
URL: https://issues.apache.org/jira/browse/HDFS-7199
Project
Jason Lowe created HDFS-7816:
Summary: Unable to open webhdfs paths with escape characters
Key: HDFS-7816
URL: https://issues.apache.org/jira/browse/HDFS-7816
Project: Hadoop HDFS
Issue Type
Jason Lowe created HDFS-11252:
-
Summary:
TestFileTruncate#testTruncateWithDataNodesRestartImmediately can fail with
BindException
Key: HDFS-11252
URL: https://issues.apache.org/jira/browse/HDFS-11252
Jason Lowe created HDFS-11251:
-
Summary: ConcurrentModificationException during
DataNode#refreshVolumes
Key: HDFS-11251
URL: https://issues.apache.org/jira/browse/HDFS-11251
Project: Hadoop HDFS
[
https://issues.apache.org/jira/browse/HDFS-11501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe resolved HDFS-11501.
---
Resolution: Invalid
JIRA is for tracking bugs against the Hadoop project and not for general user
[
https://issues.apache.org/jira/browse/HDFS-12217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe reopened HDFS-12217:
---
I reverted this from branch-2 because the commit broke the build.
{noformat}
[ERROR] COMPILATION ERROR
[
https://issues.apache.org/jira/browse/HDFS-12817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe resolved HDFS-12817.
---
Resolution: Duplicate
> Support multiple storages in DataNodeCluster / SimulatedFSData
[
https://issues.apache.org/jira/browse/HDFS-12881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe reopened HDFS-12881:
---
Reopening to get a precommit run on the branch-2 patch.
> Output streams closed with IOUtils suppress
[
https://issues.apache.org/jira/browse/HDFS-12924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe resolved HDFS-12924.
---
Resolution: Duplicate
> Port HDFS-12881 to branch-2 (Output streams closed with IOUtils suppress
Jason Lowe created HDFS-12881:
-
Summary: Output streams closed with IOUtils suppressing write
errors
Key: HDFS-12881
URL: https://issues.apache.org/jira/browse/HDFS-12881
Project: Hadoop HDFS
Jason Lowe created HDFS-13975:
-
Summary: TestBalancer#testMaxIterationTime fails sporadically
Key: HDFS-13975
URL: https://issues.apache.org/jira/browse/HDFS-13975
Project: Hadoop HDFS
Issue
[
https://issues.apache.org/jira/browse/HDFS-14084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe reopened HDFS-14084:
---
I reverted this from trunk, branch-3.2, branch-3.1, branch-3.1.2, and
branch-3.0. Heads up
85 matches
Mail list logo