Arun C Murthy created HADOOP-8429:
-
Summary: Update index.html for docs site to reflect appropriate
version in branch-2
Key: HADOOP-8429
URL: https://issues.apache.org/jira/browse/HADOOP-8429
Project
[
https://issues.apache.org/jira/browse/HADOOP-8424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy resolved HADOOP-8424.
---
Resolution: Fixed
Fix Version/s: (was: 1.1.0)
1-win
I just
in their fix versions field?
Thanks!
--
Harsh J
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
Arun C Murthy created HADOOP-8652:
-
Summary: Change website to reflect new u...@hadoop.apache.org
mailing list
Key: HADOOP-8652
URL: https://issues.apache.org/jira/browse/HADOOP-8652
Project: Hadoop
[
https://issues.apache.org/jira/browse/HADOOP-8652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy resolved HADOOP-8652.
---
Resolution: Fixed
Thanks for the review Das, I've just committed
for reducers and remaining 4 for OS and other processes.
Please correct me if my assumption is wrong.Also suggest a way to get the
optimal performance by setting these parameters. Thanks.
--
--With Regards
Pavan Kulkarni
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
knowledge of workload, black-magic and simple measurement...
*smile*
Arun
On Fri, Aug 10, 2012 at 7:34 PM, Arun C Murthy a...@hortonworks.com wrote:
Pavan,
A very important factor is how much CPU and how many spindles you have...
Your proposal for memory (44G in all) seems reasonable
[
https://issues.apache.org/jira/browse/HADOOP-8732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy resolved HADOOP-8732.
---
Resolution: Fixed
Fix Version/s: 1-win
I just committed this. Thanks Ivan
[
https://issues.apache.org/jira/browse/HADOOP-8453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy resolved HADOOP-8453.
---
Resolution: Fixed
Fix Version/s: 1-win
I just committed this. Thanks Chuan
Arun C Murthy created HADOOP-8748:
-
Summary: Move dfsclient retry to a util class
Key: HADOOP-8748
URL: https://issues.apache.org/jira/browse/HADOOP-8748
Project: Hadoop Common
Issue Type
and will be branched into branch-2.1 later
5. The release tags can have the alpha/beta tags on them.
Thoughts?
-- Owen
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
Uh, I meant 'create hadoop-2.0.2-alpha' release off branch-2.
On Sep 6, 2012, at 11:18 AM, Arun C Murthy wrote:
Sounds fine.
For now, I think we can delete branch-2.1.0-alpha, create branch-2.0.2-alpha
release off branch-2 and eventually make branch-2.1.0 as the stable release
To be clear, I think we all seem to agree that we continue to make
hadoop-2.0.3, hadoop-2.0.3 etc. with alpha/beta tags as appropriate until we
git 'GA' at which point we release hadoop-2.1.0. Makes sense?
thanks,
Arun
On Sep 6, 2012, at 11:38 AM, Arun C Murthy wrote:
Uh, I meant 'create
of that directory.
Nexus seems a bit wedged currently. I will try again to push to Nexus
tomorrow morning.
Thanks,
--Matt
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
On Sep 25, 2012, at 8:40 AM, Arun C Murthy wrote:
I'd also recommend MR-4558, MR-4328 H-8748+friends. Thoughts?
Also, MR-3837.
Initially, I didn't recommend them since I thought 1.1 was too close, but since
these (MR-3837 MR-4328 etc.) are well-baked at this point (deployed at
multiple
Yes, on it. Thanks Matt.
On Sep 25, 2012, at 9:46 AM, Matt Foley wrote:
Hi Arun,
can you get them committed to branch-1 and branch-1.1 today?
--Matt
On Tue, Sep 25, 2012 at 8:44 AM, Arun C Murthy a...@hortonworks.com wrote:
On Sep 25, 2012, at 8:40 AM, Arun C Murthy wrote:
I'd also
Point. I've opened https://issues.apache.org/jira/browse/MAPREDUCE-4687 to
track this.
On Sep 25, 2012, at 9:33 PM, Eli Collins wrote:
How about adding this step to the MR PreCommit jenkins job so it's run
as part test-patch?
On Tue, Sep 25, 2012 at 7:48 PM, Arun C Murthy
to a
script, before they disappear entirely. I would much rather see dead code
die then be maintained for a few tests that are mostly testing the dead
code itself.
--Bobby
On 9/26/12 9:39 AM, Arun C Murthy a...@hortonworks.com wrote:
Point. I've opened https://issues.apache.org/jira/browse
Guys,
A request - can everyone please set fix-version to both 2.* and 0.23.*? I
found some with only 0.23.*, makes generating release-notes very hard.
thanks,
Arun
[
https://issues.apache.org/jira/browse/HADOOP-8738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy reopened HADOOP-8738:
---
Thanks Tucu - I've reverted this to unblock 2.0.2-alpha.
junit JAR is showing
.
Thank you,
--Matt Foley
Release Manager
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
.
Thank you,
--Matt Foley
Release Manager
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
Uh, sent to wrong list...
Forgot to add: also, I successfully ran MR jobs compiled against hadoop-1.0.3
against a hadoop-1.1.0 cluster. All good.
thanks,
Arun
On Oct 9, 2012, at 6:46 AM, Arun C Murthy wrote:
+1
Verified signatures, ran randomwriter/sort on a single node (non-secure
Thanks for doing this Matt!
Arun
On Dec 5, 2012, at 12:30 AM, Matt Foley wrote:
Hi,
sorry for the thrash, but further testing in a whole-stack situation with
Hive over Hadoop-1.1.1, exposed bug
HADOOP-9115https://issues.apache.org/jira/browse/HADOOP-9115,
Deadlock in configuration when
-version for the intra-cluster protocols)
Thanks,
Eli
On Tue, Jan 29, 2013 at 12:56 PM, Arun C Murthy a...@hortonworks.com wrote:
Folks,
There has been some discussions about incompatible changes in the
hadoop-2.x.x-alpha releases on HADOOP-9070, HADOOP-9151, HADOOP-9192 and few
other
I just created branch-2.0.3-alpha.
Committers: please *do not* check-in anything else with a fix-version of
2.0.3-alpha on jira.
thanks,
Arun
[
https://issues.apache.org/jira/browse/HADOOP-9070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy resolved HADOOP-9070.
---
Resolution: Fixed
Closing again.
Kerberos SASL server cannot find
repository.apache.org.
Please try the release and vote; the vote will run for the usual 7 days.
thanks,
Arun
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
With 18 +1s (8 binding) and no -1s the vote passes.
Thanks to all who verified and voted on the release.
I'll get the bits out within the next couple of days.
thanks,
Arun
On Feb 6, 2013, at 7:59 PM, Arun C Murthy wrote:
Folks,
I've created a release candidate (rc0) for hadoop-2.0.3-alpha
,
--Matt
--
Alejandro
--
Alejandro
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
should help nevertheless.
I volunteer to do this for YARN/MapReduce (of course, any help is very much
appreciated and I see Vinod has opened YARN-386), and would appreciate some
folks stepping up for HDFS (Suresh? Todd?).
thanks,
Arun
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
[
https://issues.apache.org/jira/browse/HADOOP-9316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy resolved HADOOP-9316.
---
Resolution: Fixed
+1, lgtm. I just committed this. Thanks Mahadev!
Add
.
YARN-429 has details about the issue.
Considering this will affect all downstream projects, a new release
probably makes sense.
Thanks
- Sid
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
student,CS
Univ. of Saskatchewan
IEEE Graduate Student Member
http://homepage.usask.ca/~jac735/
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
and rest of BigTop community for
helping to find a number of integration issues, Ted Yu for co-ordinating on
HBase, Alejandro for co-ordinating on Oozie, Vinod/Sid/Alejandro/Xuan/Daryn and
rest of devs for quickly jumping and fixing these.
--
Arun C. Murthy
Hortonworks Inc.
http
-rc1/
The RC tag in svn is here:
http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.0.4-alpha-rc1
The maven artifacts are available via repository.apache.org.
Please try the release and vote; the vote will run for the usual 7 days.
thanks,
Arun
--
Arun C. Murthy
Hortonworks Inc.
http
their worth by hitting back. - Piet Hein
(via Tom White)
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
On Apr 13, 2013, at 2:42 AM, Roman Shaposhnik wrote:
On Fri, Apr 12, 2013 at 2:09 PM, Arun C Murthy a...@hortonworks.com wrote:
Sigh! You are right Andrew - I'll need to back out a patch from
branch-2.0.4-alpha and re-generate the release. RC2 needed now.
Can you elaborate please? Are you
The maven artifacts are available via repository.apache.org.
Please try the release and vote; the vote will run for the usual 7 days.
thanks,
Arun
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
will run for the usual 7 days.
thanks,
Tom Graves
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
.
Is there any document that describes the code?
Is there any way to understand the functionality of each classes and its
method?
--
*With regards ---*
*Mohammad Mustaqeem*,
M.Tech (CSE)
MNNIT Allahabad
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
With 15 +1s (8 binding), 1 -0 and no -1s the vote passes.
Thanks to all who verified the bits, I'll push them out.
thanks,
Arun
On Apr 12, 2013, at 2:56 PM, Arun C Murthy wrote:
Folks,
I've created a release candidate (RC2) for hadoop-2.0.4-alpha that I would
like to release.
The RC
by tagging features,
bug-fixes, protocol/API changes etc.? This way we can ensure HDFS APIs
protocols are locked down too - I'd really appreciate it!
thanks,
Arun
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
On Apr 25, 2013, at 6:36 PM, Suresh Srinivas wrote:
On Thu, Apr 25, 2013 at 6:34 PM, Arun C Murthy a...@hortonworks.com wrote:
Similarly on HDFS side, can someone please help out by tagging features,
bug-fixes, protocol/API changes etc.? This way we can ensure HDFS APIs
protocols
On Apr 25, 2013, at 7:31 PM, Roman Shaposhnik wrote:
On Thu, Apr 25, 2013 at 6:34 PM, Arun C Murthy a...@hortonworks.com wrote:
With that in mind, I really want to make a serious push to lock down APIs
and wire-protocols for hadoop-2.0.5-beta.
Thus, we can confidently support hadoop-2.x
Konstantin,
On Apr 26, 2013, at 4:34 PM, Konstantin Shvachko wrote:
Do you think we can call the version you proposed to release
2.1.0 or 2.1.0-beta?
The proposed new features imho do not exactly conform with the idea
of dot-dot release, but definitely qualify for a major number change.
I
Arun C Murthy created HADOOP-9517:
-
Summary: Define Hadoop Compatibility
Key: HADOOP-9517
URL: https://issues.apache.org/jira/browse/HADOOP-9517
Project: Hadoop Common
Issue Type: Bug
On Apr 26, 2013, at 12:07 PM, Eli Collins wrote:
Arun, Suresh,
Mind reviewing the following page Karthik put together on
compatibility? http://wiki.apache.org/hadoop/Compatibility
Sure. Will do.
I just opened https://issues.apache.org/jira/browse/HADOOP-9517 to ensure we
capture it for
:
On Fri, Apr 26, 2013 at 11:15 AM, Arun C Murthy a...@hortonworks.com
wrote:
On Apr 25, 2013, at 7:31 PM, Roman Shaposhnik wrote:
On Thu, Apr 25, 2013 at 6:34 PM, Arun C Murthy a...@hortonworks.com
wrote:
With that in mind, I really want to make a serious push to lock down
APIs and wire
Konstantin,
On Apr 30, 2013, at 4:28 PM, Konstantin Shvachko wrote:
Hi Arun,
I am agnostic about version numbers too, as long as the count goes up.
The discussion you are referring to is somewhat outdated, it was talking
about 2.0.4-beta, which we already passed.
It's very relevant and
On May 1, 2013, at 4:08 PM, Konstantin Shvachko wrote:
On Wed, May 1, 2013 at 1:15 PM, Arun C Murthy a...@hortonworks.com wrote:
On Apr 30, 2013, at 4:28 PM, Konstantin Shvachko wrote:
If the next release has to be 2.0.5 I would like to make an alternative
proposal, which would include
Konstantin,
On May 2, 2013, at 2:08 AM, Konstantin Shvachko wrote:
I am arguing against invasive and destructive features proposed for the
release.
Just to remind here they are again, since the history has been wiped out.
# Snapshots
# NFS gateway for HDFS
# HDFS-347 unix domain socket
there are objections, I'd like to start the vote.
Please review this release candidate and vote it for release. Vote will end
in seven days as usual, at 11:30am PDT on Monday 13 May.
Best regards,
--Matt
(release manager)
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
Folks,
A considerable number of people have expressed confusion regarding the recent
vote on 2.0.5, beta status etc. given lack of specifics, the voting itself
(validity of the vote itself, whose votes are binding) etc.
IMHO technical arguments (incompatibility b/w 2.0 2.1, current stability
Yes to all. As long as we are making timely and compatible progress, we don't
need to debate individual issues here. Let's continue discussion on relevant
jiras.
thanks,
Arun
On May 15, 2013, at 12:11 PM, Vinod Kumar Vavilapalli wrote:
- RM restart which is mostly already committed but
accidentally?
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
-a-vis 2.0.4-alpha is the
most recent example - it won't be the last.
So, I hope, concludes this meme.
thanks,
Arun
On May 15, 2013, at 2:20 PM, Arun C Murthy wrote:
Great summary, thanks Vinod.
On May 15, 2013, at 2:14 PM, Vinod Kumar Vavilapalli wrote:
Roman, I keep this same argument
on development directions without voting,
that's more evidence that the project should be split, IMO. -C
+1e100
Arun
On Wed, May 15, 2013 at 2:21 PM, Steve Loughran ste...@hortonworks.com
wrote:
On 15 May 2013 10:57, Arun C Murthy a...@hortonworks.com wrote:
Folks,
A considerable number
regressions on releases here
consistently. We've also talked in the past about running Bigtop on branch-2,
nightly. Is that something you could help with? You'd earn my personal
gratitude.
thanks,
Arun
Thanks,
Roman.
On Wed, May 15, 2013 at 3:02 PM, Arun C Murthy a...@hortonworks.com
Cos,
On May 15, 2013, at 11:38 PM, Konstantin Boudnik wrote:
What I am seeing times and again in these endless discussion threads is this:
a) downstream or bigtop: we are seeing a bunch of integration issues with
every new feature introduced/something even a commit made
b) feature
.
===
Please share your views.
Best regards,
--Matt (long-time release manager)
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
the content of the Release Candidate, in order to achieve a successful
Product Release vote.
===
Best regards,
--Matt (long-time release manager)
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
I see you just re-opened MAPREUDCE-4211.
Why not include MAPREDUCE-4211 as well rather than create one release per patch?
Also, this is the first time we are seeing a four-numbered scheme in Hadoop.
Why not call this 2.0.5-alpha?
Arun
On May 24, 2013, at 8:48 PM, Konstantin Boudnik wrote:
Sorry, it should be MAPREDUCE-5211 (not MAPREDUCE-4211).
thanks,
Arun
On May 30, 2013, at 10:57 AM, Arun C Murthy wrote:
I see you just re-opened MAPREUDCE-4211.
Why not include MAPREDUCE-4211 as well rather than create one release per
patch?
Also, this is the first time we are seeing
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 wrote:
On Thu, May 30, 2013 at 10:57 AM, Arun C Murthy
a...@hortonworks.com wrote:
Why not include MAPREDUCE
the release bits and vote; the vote will run for the 3
days,
because this is just a version name change. The bits are identical
to the
ones
voted on before in
http://s.apache.org/2041move
Thanks for your voting
Cos
--
Alejandro
--
Alejandro
--
Arun C. Murthy
I do it in the release branch, so the release source tarball has the date.
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 created. Not
sure what Matt actually does
the release and vote; the vote will run for the usual 7 days.
I am +1 (binding).
thanks,
Tom Graves
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
On Jun 5, 2013, at 11:04 AM, Roman Shaposhnik wrote
On the Bigtop side of things, once we have stable Bigtop 0.6.0 platform
based on Hadoop 2.0.x codeline we plan to start running the same battery
of integration tests on the branch-2.1-beta.
We plan to simply file JIRAs if anything gets
On Jun 4, 2013, at 8:32 AM, Arun C Murthy wrote:
Folks,
The vast majority of of the planned features and API work is complete, thanks
to everyone who contributed!
I've created a branch-2.1-beta branch from which I anticipate I can make the
first of our beta releases very shortly
we figure this
would be a good start.
Cheers,
Tim
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
As Ramya noted, things are looking good on branch-2.1-beta ATM.
Henceforth, can I please ask committers to hold off non-blocker fixes for the
final set of tests?
thanks,
Arun
On Jun 4, 2013, at 8:32 AM, Arun C Murthy wrote:
Folks,
The vast majority of of the planned features and API work
at 7:17 PM, Roman Shaposhnik r...@apache.org
wrote:
On Thu, Jun 6, 2013 at 4:48 AM, Arun C Murthy a...@hortonworks.com
wrote:
On Jun 5, 2013, at 11:04 AM, Roman Shaposhnik wrote
On the Bigtop side of things, once we have stable Bigtop 0.6.0
platform
based on Hadoop 2.0.x codeline we plan
: behavior change
status: per discussion we should first add memory-millis and vcores-millis
--
On Fri, Jun 14, 2013 at 7:17 PM, Roman Shaposhnik r...@apache.org wrote:
On Thu, Jun 6, 2013 at 4:48 AM, Arun C Murthy
14, 2013 at 7:17 PM, Roman Shaposhnik r...@apache.org
wrote:
On Thu, Jun 6, 2013 at 4:48 AM, Arun C Murthy a...@hortonworks.com
wrote:
On Jun 5, 2013, at 11:04 AM, Roman Shaposhnik wrote
On the Bigtop side of things, once we have stable Bigtop 0.6.0
platform
based on Hadoop 2.0.x
MAPREDUCE-5130?
On Sun, Jun 16, 2013 at 7:02 AM, Arun C Murthy a...@hortonworks.com wrote:
On Jun 16, 2013, at 5:39 AM, Arun C Murthy wrote:
On Jun 15, 2013, at 8:19 AM, Alejandro Abdelnur wrote:
Of the JIRAs in my laundry list for 2.1 the ones I would really want in
are
YARN
Responses inline:
On Jun 16, 2013, at 1:04 PM, Roman Shaposhnik wrote:
But there's a bit of bad news too (or at least the news that need to
be triaged). At
this point I don't know whether the Hadoop code is to blame or the
tests/components
themselves -- all I know is that these tests passed
Roman,
Is there a chance you can run the tests with the full stack built against
branch-2.1-beta and help us know where we are?
thanks,
Arun
On Jun 16, 2013, at 4:50 PM, Arun C Murthy wrote:
Responses inline:
On Jun 16, 2013, at 1:04 PM, Roman Shaposhnik wrote:
But there's a bit
Ping. Any luck?
On Jun 17, 2013, at 4:06 PM, Roman Shaposhnik r...@apache.org wrote:
On Sun, Jun 16, 2013 at 5:14 PM, Arun C Murthy a...@hortonworks.com wrote:
Roman,
Is there a chance you can run the tests with the full stack built against
branch-2.1-beta and help us know where we
, Arun C Murthy a...@hortonworks.com
wrote:
Ping. Any luck?
Unfortunately I've ran into:
https://issues.apache.org/jira/browse/HADOOP-9654
which was caused by the unrelated memory pressure on the NN,
but it had an unfortunate side effect of making the rest of the
testing stuck. I'll
Ok, the last of the blockers is done.
I'll roll an RC tonight.
thanks,
Arun
On Jun 20, 2013, at 2:40 PM, Arun C Murthy a...@hortonworks.com wrote:
I think I've shared this before, but here you go again…
http://s.apache.org/hadoop-2.1.0-beta-blockers
At this point, HADOOP-9421 seems like
/release-2.1.0-beta-rc0
The maven artifacts are available via repository.apache.org.
Please try the release and vote; the vote will run for the usual 7 days.
thanks,
Arun
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
bit that blocks the Bigtop side of things as far as
2.1 is concerned.
Thanks,
Roman.
On Wed, Jun 26, 2013 at 1:17 AM, Arun C Murthy a...@hortonworks.com wrote:
Folks,
I've created a release candidate (rc0) for hadoop-2.1.0-beta that I would
like to get released.
This release
did not create a JIRA version I cannot close those JIRAs.
Can we please create the JIRA versions? later we can rename them.
Thx
--
Alejandro
--
http://hortonworks.com/**download/ http://hortonworks.com/download/
--
Alejandro
--
Arun C. Murthy
Hortonworks Inc
)
On Tue, Jul 9, 2013 at 10:54 AM, Arun C Murthy a...@hortonworks.com wrote:
On Jul 2, 2013, at 3:54 PM, Alejandro Abdelnur t...@cloudera.com wrote:
We need clarification on this then.
I was under the impression that branch-2 would be 2.2.0.
Sorry, I missed this thread - thanks
Arun C Murthy created HADOOP-9800:
-
Summary: Fix up mvn src profile
Key: HADOOP-9800
URL: https://issues.apache.org/jira/browse/HADOOP-9800
Project: Hadoop Common
Issue Type: Bug
tag in svn is here:
http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.1.0-beta-rc1
The maven artifacts are available via repository.apache.org.
Please try the release and vote; the vote will run for the usual 7 days.
thanks,
Arun
--
Arun C. Murthy
Hortonworks Inc.
http
project.
That in mind, can anybody hold my hand for a few commits to get me rolling?
Thanks,
John Chilton
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
-9816. I think I understand the problem and it shouldn't be hard to
fix.
The bug went unnoticed because sadly there are no unit tests for the QOP
options, even though it just involves a conf setting.
Daryn
On Jul 29, 2013, at 5:00 PM, Arun C Murthy wrote:
Ok, I think we are close
/repos/asf/hadoop/common/tags/release-2.1.0-beta-rc2
The maven artifacts are available via repository.apache.org.
Please try the release and vote; the vote will run for the usual 7 days.
thanks,
Arun
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
--
CONFIDENTIALITY NOTICE
NOTICE
From: Arun C Murthy a...@hortonworks.com
To: common-dev@hadoop.apache.org common-dev@hadoop.apache.org;
hdfs-...@hadoop.apache.org hdfs-...@hadoop.apache.org;
mapreduce-...@hadoop.apache.org mapreduce-...@hadoop.apache.org;
yarn-...@hadoop.apache.org yarn-...@hadoop.apache.org
Sent
with
security.
Kihwal
From: Arun C Murthy a...@hortonworks.com
To: common-dev@hadoop.apache.org common-dev@hadoop.apache.org;
hdfs-...@hadoop.apache.org hdfs-...@hadoop.apache.org;
mapreduce-...@hadoop.apache.org mapreduce-...@hadoop.apache.org;
yarn
'
for the final hadoop-2 GA release. I don't mean to jinx it but saying it out
loud, but I feel we could look at pushing out hadoop-2 GA by mid-September…
there I said it! *smile*
Thoughts?
thanks,
Arun
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
--
CONFIDENTIALITY NOTICE
NOTICE
?
Thanks in advance,
Elizabeth
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from
FYI - here is the end-point I'm using to track blockers on 2.1.1-beta:
http://s.apache.org/hadoop-2.1.1-beta-blockers
Essentially, these are *Blocker* bugs with *Target Version* set to 2.1.1-beta.
thanks,
Arun
On Aug 16, 2013, at 7:39 PM, Arun C Murthy a...@hortonworks.com wrote:
Gang,
I
as-is, we should be sure to change the fix version field on that
JIRA to be correct.
--
Aaron T. Myers
Software Engineer, Cloudera
On Thu, Aug 15, 2013 at 2:15 PM, Arun C Murthy a...@hortonworks.com wrote:
Folks,
I've created a release candidate (rc2) for hadoop-2.1.0-beta that I would
are available via repository.apache.org.
The only difference between rc0 and rc1 is ASL added to releasenotes.html and
updated release dates in CHANGES.txt files.
Please try the release bits and vote; the vote will run for the usual 7 days.
Thanks for your voting
Cos
--
Arun C. Murthy
of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use
With 9 +1s including mine (6 binding) and no -1s, the vote passes. Thanks to
all who voted.
Arun
On Aug 15, 2013, at 2:15 PM, Arun C Murthy a...@hortonworks.com wrote:
Folks,
I've created a release candidate (rc2) for hadoop-2.1.0-beta that I would
like to get released - this fixes
I'm planning on creating a branch-2.1.1-beta by EOD today. Ok?
thanks,
Arun
On Aug 16, 2013, at 7:39 PM, Arun C Murthy a...@hortonworks.com wrote:
Gang,
I spent time looking through changes slated for hadoop-2.1.1-beta and things
look fairly contained (~10 or so changes for each
1 - 100 of 274 matches
Mail list logo
