On Wed, May 18, 2016 at 08:29AM, Allen Wittenauer wrote:
> That’s really a question for infrastructure-...@apache.org . They
> manage the ASF build infrastructure which Apache Hadoop and lots of
> other projects utilize. (Bigtop uses something custom, which I think
> is fun
[
https://issues.apache.org/jira/browse/MAPREDUCE-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik resolved MAPREDUCE-2230.
---
Resolution: Won't Fix
Release Note: AOP tests were removed fro
All,
I have pushed the bits of 2.0.6-alpha into the open and released staging bits
in Nexus. Site is updated with the release news.
2.0.6-alpha is officially live now. Thanks everybody for your help!
Cos
On Thu, Aug 22, 2013 at 11:09PM, Konstantin Boudnik wrote:
> I am clearly +1 (
I am clearly +1 (non-binding) on the release.
With 8 +1s (5 binding), no -1s or 0s the vote passes.
Thanks to all who verified the bits, I'll push them out shortly.
Thanks,
Cos
On Thu, Aug 15, 2013 at 10:29PM, Konstantin Boudnik wrote:
> All,
>
> I have created a release candi
All,
I have created a release candidate (rc1) for hadoop-2.0.6-alpha that I would
like to release.
This is a stabilization release that includes fixed for a couple a of issues
as outlined on the security list.
The RC is available at: http://people.apache.org/~cos/hadoop-2.0.6-alpha-rc1/
The RC t
:check passes on the RC before publishing
> it.
>
> Arun, as you are about to cut the new RC for 2.1.0-beta, can you please
> make sure the license headers are used in the releasenotes HTML files?
>
> Thx
>
>
> On Thu, Aug 15, 2013 at 8:02 PM, Konstantin
the NO OK points (specially the last one), they
> are trivial.
>
> Thanks.
>
>
>
> On Sat, Aug 10, 2013 at 5:46 PM, Konstantin Boudnik wrote:
>
> > All,
> >
> > I have created a release candidate (rc0) for hadoop-2.0.6-alpha that I
> > would
> &
don't have license
> headers,
>
> I think we need to address the NO OK points (specially the last one), they
> are trivial.
>
> Thanks.
>
>
>
> On Sat, Aug 10, 2013 at 5:46 PM, Konstantin Boudnik wrote:
>
> > All,
> >
> > I have created
All,
I have created a release candidate (rc0) for hadoop-2.0.6-alpha that I would
like to release.
This is a stabilization release that includes fixed for a couple a of issues
as outlined on the security list.
The RC is available at: http://people.apache.org/~cos/hadoop-2.0.6-alpha-rc0/
The RC t
I am clearly +1 (non-binding) on the release.
With 8 +1s (3 binding), no -1s or 0s the vote passes.
Thanks to all who verified the bits, I'll push them out shortly.
Thanks,
Cos
On Mon, Jun 03, 2013 at 12:51PM, Konstantin Boudnik wrote:
> I have rolled out release candidate (rc2) fo
signatures, built, ran
> single node cluster.
>
> Thanks,
> Tom
>
>
>
> On 6/3/13 2:51 PM, "Konstantin Boudnik" wrote:
>
> >I have rolled out release candidate (rc2) for hadoop-2.0.5-alpha.
> >
> >The difference between rc1 and rc2 is th
te before 06/06/2013 5pm PDT.
Thanks for your patience!
Cos
On Fri, May 31, 2013 at 09:27PM, Konstantin Boudnik wrote:
> All,
>
> I have created a release candidate (rc1) for hadoop-2.0.5-alpha that I would
> like to release.
>
> This is a stabilization release that i
Ok, if this the consensus on the issue, then tonight I will cut rc2 with only
CHANGES.txt release dates update. After that I will extend the vote once
again.
Sorry for the hassle to all who did voted before.
Cos
On Mon, Jun 03, 2013 at 12:18AM, Doug Cutting wrote:
> On Sun, Jun 2, 2013 at 9:01
out it I will alter the CHANGES.txt
files
thanks,
Cos
> Arun
>
> On Jun 2, 2013, at 6:41 PM, Konstantin Boudnik wrote:
>
> > On Sun, Jun 02, 2013 at 03:04PM, Arun C Murthy wrote:
> >> I record the 'release date' as the one on which the build is crea
hes, ie branch-2 and trunk. Am I correct?
Thanks,
Cos
> hth,
> Arun
>
> On Jun 2, 2013, at 12:33 PM, Konstantin Boudnik wrote:
>
> > This is my first Hadoop release, so I am all ears ;) I looked at how Arun
> > was
> > cutting the previous 2.0.x and followed
asy way to solve it it would be
> using as release date the date the vote ends. Anyway, not a big deal if we
> are not cutting a new rc for other reason
>
> +1 on rc1
>
> Thx
>
> On Jun 2, 2013, at 12:04 AM, Konstantin Boudnik wrote:
>
> > Alejandro,
> &
ttp://people.apache.org/~cos/hadoop-2.0.5-alpha-rc1/
> > looks good to me.
> > +1 (non-binding)
> >
> > Thanks,
> >
> > Joep
> >
> >
> > On Fri, May 31, 2013 at 8:25 PM, Konstantin Boudnik
> > wrote:
> >
> > > Ok, WRT HDFS-
I changes are completed, I have updated branch-2 and trunk CHANGES.txt files
as planned. Version of the branch-2 is set to 2.1.0-beta; 2.0.5-alpha release
artifacts are deployed to the staging area.
Thanks for your patience, guys!
Cos
On Fri, May 31, 2013 at 12:45PM, Konstantin Boudnik wrote
Chris,
with 2.0.5-alpha (rc1) out, would you please take a look at the release bits?
I assume the four-digit numbering scheme issue has been resolved now.
Regards,
Cos
On Thu, May 30, 2013 at 06:18PM, Chris Douglas wrote:
> On Thu, May 30, 2013 at 5:51 PM, Konstantin Boudnik wrote:
&g
All,
I have created a release candidate (rc1) for hadoop-2.0.5-alpha that I would
like to release.
This is a stabilization release that includes fixed for a couple a of issues
discovered in the testing with BigTop 0.6.0 release candidate.
The RC is available at: http://people.apache.org/~cos/had
that you guys have noted
earlier and will be re-spinning RC1 in a few.
Cos
On Fri, May 31, 2013 at 08:07PM, Konstantin Boudnik wrote:
> Alejandro,
>
> thanks for looking into this. Indeed - I missed the 2.0.5-alpha section in
> YARN CHANGES.txt. Added now. As for HDFS-4646: appare
oes not have the 2.0.5-alpha section (it should
> be there empty).
>
> Cos, can you please look at these 2 things and explain/fix?
>
> Thanks.
>
>
>
> On Fri, May 31, 2013 at 4:04 PM, Konstantin Boudnik wrote:
>
> > All,
> >
> > I have create
All,
I have created a release candidate (rc0) for hadoop-2.0.5-alpha that I would
like to release.
This is a stabilization release that includes fixed for a couple a of issues
discovered in the testing with BigTop 0.6.0 release candidate.
The RC is available at: http://people.apache.org/~cos/had
, 2013 at 12:45 PM, Konstantin Boudnik wrote:
>
> > Guys,
> >
> > I will be performing some changes wrt to moving 2.0.4.1 release candidate
> > to
> > 2.0.5 space. As outline below by Alejandro:
> >
> > 1. I will create new 2.0.5-alpha branch from the current
Guys,
I will be performing some changes wrt to moving 2.0.4.1 release candidate to
2.0.5 space. As outline below by Alejandro:
1. I will create new 2.0.5-alpha branch from the current head of 2.0.4-alpha
that contains 2.0.4.1 changes
2. consequently, set the artifacts version on the new branch to
o 2.0.5-alpha versions
> in jira for HADOOP, HDFS, YARN & MAPREDUCE.
>
> Please take care of the rest.
>
> Also, in branch-2, the version should be 2.1.0-SNAPSHOT.
>
> thanks,
> Arun
>
> >
> > Thanks.
> >
> >
> > On Thu, May 30, 20
urrent 2.0.5 version in JIRA to 2.1.0, create a new 2.0.5
> version, change the fix version of the 2 JIRAs that make the RC
>
> Thanks.
>
>
> On Thu, May 30, 2013 at 6:18 PM, Chris Douglas wrote:
>
> > On Thu, May 30, 2013 at 5:51 PM, Konstantin Boudnik
> > wr
On Thu, May 30, 2013 at 05:30PM, Chris Douglas wrote:
> On Thu, May 30, 2013 at 3:25 PM, Konstantin Boudnik wrote:
> > There's no plans to release anything else at this point - this is a bug-fix
> > release, as I pointed out on a numerous occasions. There's no new fe
tml
>
> 0.17.2 was missing some native libs so 0.17.2.1 was released to fix
> that critical issue instead of calling it .3
Exactly the point - the _bigfix_ release. Thanks for pointing out the
similarities.
Cos
>
> J-D
>
> On Thu, May 30, 2013 at 3:52 PM, Konstantin Boudnik
that's standard
> usage. Whoever makes the 2.0.5 release (or any "next" release) is expected
> to update the parent branch's SNAPSHOT default versioning, per
> HowToReleasePostMavenization#Branching<https://wiki.apache.org/hadoop/HowToReleasePostMavenization#Branching&
On Thu, May 30, 2013 at 03:18PM, Chris Douglas wrote:
> On Thu, May 30, 2013 at 2:39 PM, Konstantin Boudnik wrote:
> > There's no misunderstanding Chris - this release is to unblock downstream.
> >
> > As for your question: I don't have a crystal ball; I wish thou
is the first time we are seeing a four-numbered scheme in
> > Hadoop. Why not call this 2.0.5-alpha?
>
> Good point. Since it contains only backports from branch-2, it would
> make sense for it to be an intermediate release.
>
> I shouldn't have to say this, but I&
re very confusing. Some of them never been concluded, the
branches are moved and artifact versions seem to be colliding. 2.0.4.x seems
to work well for the stabilization purposes and it will allow to unblock
downstream and integration projects quickly.
Cos
> Arun
>
> On May 24, 2013, at 8:48 P
[
https://issues.apache.org/jira/browse/MAPREDUCE-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik reopened MAPREDUCE-5211:
---
This needs to go into the next stabilization release of 2.0.4.2 as well
All,
I have created a release candidate (rc0) for hadoop-2.0.4.1-alpha that I would
like to release.
This is a stabilization release that includes fixed for a couple a of issues
discovered in the testing with BigTop 0.6.0 release candidate.
The RC is available at: http://people.apache.org/~cos/h
[
https://issues.apache.org/jira/browse/MAPREDUCE-5240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik reopened MAPREDUCE-5240:
---
I will be backporting this to 2.0.4.1 release
> inside
I have put together this chart some time ago and am trying to keep it up to
date (more or less). The most latest update is available here:
http://is.gd/axRlgJ
Sometimes picture worth a lot... you know ;)
Cos
On Fri, Apr 26, 2013 at 11:09AM, Suresh S wrote:
> Hello,
>
> I was confus
On Mon, Apr 22, 2013 at 10:51AM, Sangjin Lee wrote:
> Hi,
>
> I just wanted to ping the committers again for your review of the patch for
> MAPREDUCE-5069. I would greatly appreciate it if you could take a look at
> the patch, and let me know if you have any feedback or accept the patch.
>
> On a
-0
the release is missing HADOOP-9704 that has critical effect on downstream
projects e.g. build are affected. The issue has been raised for the first time
back in 4/10/13 http://is.gd/OGb3GG and never been even sneezed upon.
Cos
On Sat, Apr 13, 2013 at 03:26AM, Arun C Murthy wrote:
> Folks,
>
[
https://issues.apache.org/jira/browse/MAPREDUCE-5088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik resolved MAPREDUCE-5088.
---
Resolution: Fixed
The patch is merged to all corresponding branches now
Here's a daily build for hadoop-2 branch
https://builds.apache.org/job/Hadoop-branch2
It just builds the full Hadoop project without running any tests (for now).
Can be easily extended to do test runs/artifact deployment, if needed.
Cos
On Mon, Mar 25, 2013 at 07:14PM, Konstantin Bo
ache.org/jira/browse/HDFS-4615?focusedCommentId=13612650&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13612650
>
> Regards,
> Suresh
>
>
> On Mon, Mar 25, 2013 at 1:17 PM, Konstantin Boudnik wrote:
>
> > It doesn't look like any progress
Konstantin Boudnik created MAPREDUCE-5101:
-
Summary: hive smoke tests can
Key: MAPREDUCE-5101
URL: https://issues.apache.org/jira/browse/MAPREDUCE-5101
Project: Hadoop Map/Reduce
It doesn't look like any progress has been done on the ticket below in the
last 3 weeks. And now branch-2 can't be compiled because of
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestDFSShell.java:[895,15]
WINDOWS is not public in org.apache.hadoop.fs.Path; cannot be acce
t; > Making two builds is less than 2 days work, imho, given that there is
> > a Windows node available and that mvn targets are in place. Correct me
> > if I missed any complications in the process.
>
> On Fri, Mar 1, 2013 at 3:47 PM, Konstantin Boudnik wrote:
> > It seems t
Suresh, I appreciate all the troubles you're going through wrt syncing up the
huge patch for a long time - I really do.
I am not asking to have full test-patch process in place. But I think it is a
real good idea to have a way to run the full test suite once in a while - or
as Konstantin proposing
It seems that with the HW in place, the matter of setting at least nightly
build is trivial for anyone with up to date Windows knowledge. I wish I could
help. Going without a validation is a recipe for a disaster IMO.
-1 until some reasonable solution is implemented.
Cos
On Fri, Mar 01, 2013 at
On Thu, Feb 28, 2013 at 03:08PM, sanjay Radia wrote:
> +1
> Java has done the bulk of the work in making Hadoop multi-platform.
> Windows specific code is a tiny percentage of the code.
> Jeninks support for windows is going help us keep the platform portable going
> forward.
> I expect that the v
What was wrong with surefire.timeout in the build system? Why coming up with
artificial enforcements like this?
Cos
On Fri, Feb 22, 2013 at 08:35AM, Surenkumar Nihalani wrote:
> Hey Tsuyoshi,
>
> The check for timeout in @Tests was recently introduced. This was a bug of
> the first commit. A co
On Tue, Feb 12, 2013 at 07:44PM, Konstantin Boudnik wrote:
> We've created BigTop stack with 2.0.3 as the base. Ran YCSB, slive, and some
> other loads on up to 20 nodes clusters as a part of the release validation.
> Two issues were noted:
>
> - due to the known issue with Je
We've created BigTop stack with 2.0.3 as the base. Ran YCSB, slive, and some
other loads on up to 20 nodes clusters as a part of the release validation.
Two issues were noted:
- due to the known issue with Jetty we are seeing MR jobs hanging here and
there
- without properly configured capacity-
The issue with the configuration is raised (and adressed) in
https://issues.apache.org/jira/browse/BIGTOP-841
Cos
On Fri, Feb 08, 2013 at 04:25PM, Aaron T. Myers wrote:
> +1 (binding)
>
> I downloaded the src tar ball, built it with the native bits enabled,
> started up a little cluster, and
might different opinions in the community, as
f course, I don't see any real issues with that approach.
Cos
> Thanks,
> Tsuyoshi
>
> On Wed, Jan 16, 2013 at 12:13 PM, Konstantin Boudnik wrote:
> > Hadoop-1 includes framework called Herriot that would allow you to develop
&
Hadoop-1 includes framework called Herriot that would allow you to develop
on-the-cluster FI system tests. However, because of the some timing, it hasn't
been hooked into the maven build system Hadoop-2 branches.
Basically, I see two way of doing what you need to do here:
- wait until the Herrio
h of
> test-system is such that these tests are being run before FI tests and so
> its failing before reaching FI tests. Are you able to run these
> successfully, and if yes, how?
>
> Thanks
> Ravi
>
>
> On Mon, May 7, 2012 at 5:47 PM, Konstantin Boudnik wrote:
>
> &g
ib/block_forensics :
> hadoop-mapreduce/src/contrib/vaidya :
> hadoop-mapreduce/src/contrib/vertica :
>
> thx.
>
>
> On Thu, May 17, 2012 at 9:15 AM, Konstantin Boudnik wrote:
> > Herriot and fault injection work is still due, although it won't affect
>
Herriot and fault injection work is still due, although it won't affect the
build if these files will be removed.
Cos
On Thu, May 17, 2012 at 09:12AM, Alejandro Abdelnur wrote:
> First of all, Thomas, thanks for finalizing Gridmix mavenization.
>
> AFAIK this was the blocker to get rid of the An
Hi Ravi.
You need to run Herriot build to make sure that everything is ok after your
changes. The way to to it is as follows:
% ant jar-system jar-test-system
this will perform the compilation of Hadoop binaries with weaved Herriot APIs.
More information about Herriot can be found here
ht
[
https://issues.apache.org/jira/browse/MAPREDUCE-3863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik resolved MAPREDUCE-3863.
---
Resolution: Fixed
Fix Version/s: 0.22.1
Hadoop Flags
TLDR :/
Besides, it isn't a job list
Cos
On Mon, Apr 09, 2012 at 10:59PM, Bing Li wrote:
> 国际著名大型IT企业（排名前3位）开发中心招聘Hadoop技术专家（北京）-非猎头
>
> 职位描述：
> Hadoop系统和平台开发（架构师，资深开发人员）
>
>
> 职位要求：
>
> 1.有设计开发大型分布式系统的经验（工作年限3年以上，架构师5年以上），hadoop大型实际应用经验优先
>
> 2.良好的编程和调试经验(java or c++/c)，扎实的计算机理论基础，快速的学习能力
[
https://issues.apache.org/jira/browse/MAPREDUCE-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik resolved MAPREDUCE-2344.
---
Resolution: Won't Fix
As in HDFS-798
> Exclud
[
https://issues.apache.org/jira/browse/MAPREDUCE-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik resolved MAPREDUCE-3429.
---
Resolution: Fixed
Hadoop Flags: Reviewed
I have just committed it
Map/Reduce
Issue Type: Bug
Components: contrib/capacity-sched, contrib/gridmix
Affects Versions: 0.22.0
Reporter: Konstantin Boudnik
Assignee: Konstantin Boudnik
Fix For: 0.22.0
As the result of MAPREDUCE-3311 fix a transient {{commons
[
https://issues.apache.org/jira/browse/MAPREDUCE-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik resolved MAPREDUCE-3311.
---
Resolution: Fixed
Hadoop Flags: Reviewed
I have just committed the
[
https://issues.apache.org/jira/browse/MAPREDUCE-3396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik resolved MAPREDUCE-3396.
---
Resolution: Duplicate
It really dups MAPREDUCE-3311, so closing this one
/mumak
Affects Versions: 0.22.0
Reporter: Konstantin Boudnik
Assignee: Konstantin Boudnik
Fix For: 0.22.0
{{contrib/mumak}} compilation is broken because of the missing {{commons-lang}}
dependency
--
This message is automatically generated by JIRA.
If you
Reporter: Konstantin Boudnik
Assignee: Konstantin Boudnik
Fix For: 0.22.0
MapReduce part of HADOOP-7450
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure
[
https://issues.apache.org/jira/browse/MAPREDUCE-3156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik resolved MAPREDUCE-3156.
---
Resolution: Fixed
Fix Version/s: 0.22.0
Hadoop Flags
Affects Versions: 0.22.0
Reporter: Konstantin Boudnik
Assignee: Konstantin Boudnik
Mapreduce part of HDFS-1762
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org
Seems like it has been broken in the recent re-shuffle of the workspace due to
the maven changes. This external now lives under hadoop-common, apparently.
On Sun, Aug 21, 2011 at 07:20PM, Praveen Sripati wrote:
> Hi,
>
> When I try to get the code from svn, I get the below error.
>
> svn co http
oop, I guess you are the best person to
> take care of this part of the puzzle.
>
> Thanks.
>
> Alejandro
>
> On Fri, Aug 19, 2011 at 11:09 AM, Konstantin Boudnik wrote:
>
> > I see that the whole AOP stuff has been taken out along with Herriot work.
> > I d
I see that the whole AOP stuff has been taken out along with Herriot work.
I don't see any discussion about this on the JIRA. Neither I don't see any
tickets created to track the effort (but a subtask for FI tests in
HADOOP-7412).
Any reason we are missing a big chunk of validation infrastructure
[
https://issues.apache.org/jira/browse/MAPREDUCE-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik resolved MAPREDUCE-2752.
---
Resolution: Fixed
Fix Version/s: 0.22.0
Hadoop Flags
[
https://issues.apache.org/jira/browse/MAPREDUCE-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik resolved MAPREDUCE-2547.
---
Resolution: Not A Problem
> TestDFSIO fails on a physical clus
Versions: 0.22.0
Environment: Physical cluster based on 0.22-SNAPSHOT
Reporter: Konstantin Boudnik
An attempt to run TestDSFIO on cluster fails because TestDFSIO tries to run MR
job with local runner. If JT is explicitly specified via {{-jt}} cmd. arg. then
everything is
[
https://issues.apache.org/jira/browse/MAPREDUCE-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik resolved MAPREDUCE-1614.
---
Resolution: Duplicate
This has been fixed by MAPREDUCE-1832
http://hadoop.apache.org/mapreduce will be a great starting point for you.
--
Take care,
Konstantin (Cos) Boudnik
On Sat, Apr 30, 2011 at 09:14, shashank shekhar wrote:
> hii.i want to contribute to mapreduce but i now i am in beginner stage so i
> have few question for which i need answer.
[
https://issues.apache.org/jira/browse/MAPREDUCE-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik resolved MAPREDUCE-2202.
---
Resolution: Fixed
Patch has been reviewed as a part of parent issue. I
m triggering a build to verify this.
>
> -Giri
>
>
> On 3/4/11 4:21 PM, "Giridharan Kesavan" wrote:
>
>> I'm lookin into it..
>> -Giri
>>
>> On 3/4/11 3:04 PM, "Konstantin Boudnik" wrote:
>>
>>> Looks like the same sym
Looks like the same symptoms are affecting Common trunk builds
https://hudson.apache.org/hudson/job/Hadoop-Common-trunk-Commit/516/
Have our build env. has been changed recently?
--
Take care,
Konstantin (Cos) Boudnik
On Thu, Mar 3, 2011 at 21:36, Konstantin Boudnik wrote:
> That seems l
That seems like settings.xml has been modified, but then it'd affect
other builds as well. Unless we are using different machines/users for
different component's builds.
On Thu, Mar 3, 2011 at 13:41, Todd Lipcon wrote:
> Anyone understand why we can't seem to publish to apache maven anymore?
>
>
Reporter: Konstantin Boudnik
Assignee: Konstantin Boudnik
Priority: Minor
Attachments: MAPREDUCE-2344.patch
Counterpart of HDFS-798
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Moving hdfs-dev@ and mapreduce-dev@ to Bcc: to avoid cross-postings.
>From what I understand you want to have a test case which demonstrates
that whatever socket/stream connections were opened are properly
closed in case of IOException? I guess one of many possibilities would
be to check if a conn
[
https://issues.apache.org/jira/browse/MAPREDUCE-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik resolved MAPREDUCE-2228.
---
Resolution: Fixed
Fix Version/s: 0.21.1
Hadoop Flags
[
https://issues.apache.org/jira/browse/MAPREDUCE-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik resolved MAPREDUCE-2223.
---
Resolution: Fixed
Fix Version/s: 0.21.1
Hadoop Flags
://issues.apache.org/jira/browse/MAPREDUCE-2202
Project: Hadoop Map/Reduce
Issue Type: Improvement
Affects Versions: 0.23.0
Reporter: Konstantin Boudnik
Assignee: Konstantin Boudnik
Counterpart of HADOOP-7014 and HDFS-1486
--
This message is automatically
-2200
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: test
Affects Versions: 0.23.0
Reporter: Konstantin Boudnik
TestUmbilicalProtocolWithJobToken requires Krb environment to be set. For
testing some 'pseudo' environment is needed (
[
https://issues.apache.org/jira/browse/MAPREDUCE-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik resolved MAPREDUCE-2199.
---
Resolution: Fixed
Hadoop Flags: [Reviewed]
I have just committed
[
https://issues.apache.org/jira/browse/MAPREDUCE-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik resolved MAPREDUCE-2195.
---
Tags: herriot
Resolution: Fixed
Fix Version/s: 0.22.0
Issue Type: Bug
Components: test
Affects Versions: 0.22.0
Environment: herriot
Reporter: Konstantin Boudnik
Assignee: Konstantin Boudnik
As its counter-part HDFS-1167: new parameter needs to be added to the
system-test configuration file
[
https://issues.apache.org/jira/browse/MAPREDUCE-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik resolved MAPREDUCE-2134.
---
Resolution: Fixed
Fix Version/s: 0.21.1
Hadoop Flags
: 0.21.1
Reporter: Konstantin Boudnik
Assignee: Konstantin Boudnik
Build failed due to unable to copy the commons instrumented jar. I could see
the following error in the log.
binary-system:
[copy] Copying 5 files to
/home/vinay/mapreduce/build-fi/system/hadoop-mapred
[
https://issues.apache.org/jira/browse/MAPREDUCE-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik resolved MAPREDUCE-2090.
---
Release Note: This fix requires that test coverage is running under
[
https://issues.apache.org/jira/browse/MAPREDUCE-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik resolved MAPREDUCE-1984.
---
Hadoop Flags: [Reviewed]
Assignee: Balaji Rajagopalan
Fix
Trunk can't be compiled
---
Key: MAPREDUCE-2092
URL: https://issues.apache.org/jira/browse/MAPREDUCE-2092
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: tasktracker
Reporter: Konst
[
https://issues.apache.org/jira/browse/MAPREDUCE-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik resolved MAPREDUCE-1154.
---
Resolution: Duplicate
This has been addressed as HADOOP-6332 and derived
[
https://issues.apache.org/jira/browse/MAPREDUCE-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik resolved MAPREDUCE-1942.
---
Hadoop Flags: [Reviewed]
Fix Version/s: 0.21.0
Resolution
Type: Bug
Components: build
Affects Versions: 0.21.0
Reporter: Konstantin Boudnik
Assignee: Konstantin Boudnik
Priority: Minor
Similar to HDFS-1299: prevent calls to helper targets.
--
This message is automatically generated by JIRA.
-
You can rep
Components: build
Affects Versions: 0.21.0
Reporter: Konstantin Boudnik
Assignee: Konstantin Boudnik
Similar to that of HDFS-1199 for MapReduce.
Adds an ability to run up to 30 minutes of the tests to 'smoke' MapReduce build
i.e. find possible issues f
build
Affects Versions: 0.21.0
Reporter: Konstantin Boudnik
Similar to HDFS-1177 Ivy needs to be upgraded up to 2.1
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
1 - 100 of 113 matches
Mail list logo
