+1.
thanks
mahadev
On Tue, May 21, 2013 at 4:48 PM, Karthik Kambatla ka...@cloudera.com wrote:
+1 (non-binding)
On Tue, May 21, 2013 at 4:13 PM, Jitendra Pandey
jiten...@hortonworks.comwrote:
+1
On Tue, May 21, 2013 at 4:02 PM, Eli Collins e...@cloudera.com wrote:
+1 thanks Matt.
Project: Hadoop Common
Issue Type: Bug
Affects Versions: 0.23.0
Reporter: Mahadev konar
Assignee: Mahadev konar
Fix For: 0.23.1
We need to add a property for History server protocol in hadoop-policy.xml for
service level auth.
--
This message
+1 ran a single node cluster and a couple of examples on it. Also ran ant
tests.
thanks
mahadev
On Thu, Dec 22, 2011 at 10:23 AM, Arun C Murthy a...@hortonworks.com wrote:
+1
Checked sigs, ran a single node cluster and tests.
Arun
On Dec 18, 2011, at 11:18 PM, Matt Foley wrote:
Okay
Praveen,
There is a fix being worked on in HADOOP-7843.
Hope that helps.
thanks
mahadev
On Mon, Nov 21, 2011 at 8:48 AM, Praveen Sripati
praveensrip...@gmail.com wrote:
Harsh,
Branch-0.23 has File workDir; while the trunk has final File workDir;
in RunJar.java.
For the 0.23 build, should
Milind,
Great news. Any chance you can upload a patch as it is? I am sure,
others can help cleaning it up. I am willing to help smoothen it out
and am sure Ralph can provide feedback as well.
thanks
mahadev
On Mon, Nov 21, 2011 at 3:47 PM, milind.bhandar...@emc.com wrote:
Hi Ralph,
I spoke
Moving it to mapreduce-user.
Ronnie,
Is jobclient.getalljobs() something that you are looking for?
thanks
mahadev
On Sat, Nov 12, 2011 at 7:08 AM, Ronnie Dove ron...@oceansync.com wrote:
Hello,
Is it possible to connect to an already running JobTracker via socket through
the Hadoop Java
Thanks Giri!
mahadev
On Fri, Oct 14, 2011 at 3:30 PM, giridharan kesavan
gkesa...@hortonworks.com wrote:
Okay, I ve done the 0.23 commit setup.
Builds up and running for common/hdfs and Mapred
https://builds.apache.org/view/G-L/view/Hadoop/job/Hadoop-Common-0.23-Commit/
+1. Downloaded the bits, set up a single node cluster and ran example
jobs. Works fine.
thanks
mahadev
On Thu, Oct 13, 2011 at 5:46 PM, Aaron T. Myers a...@cloudera.com wrote:
+1 (non-binding)
I downloaded the tar ball and deployed on a 6 node cluster with security
disabled. I put a few
Versions: 0.23.0
Reporter: Mahadev konar
Assignee: Mahadev konar
Priority: Critical
Fix For: 0.23.0
hadoop-auth-examples/pom.xml has references to 0.24 in the 0.23 branch.
--
This message is automatically generated by JIRA.
For more information
+1.
Downloaded the release, brought up a single node cluster and ran a
randomwriter job. Also ran ant test and it passed.
thanks
mahadev
On Aug 26, 2011, at 10:08 AM, Eric Yang wrote:
+1 (non-binding), tested several map reduce jobs on 50 nodes with security
enabled. No failure observed
Jokes aside,
I intend to try it out on a set of 10 nodes or so and see if it works or not.
If it works fine (barring a few task failures), I dont see any reason why this
cannot be released.
thanks
mahadev
On Aug 18, 2011, at 11:35 AM, Jakob Homan wrote:
This vote is still running with no
Allen,
I think Giri already sent out an email for that. Below is the
response from him. There'll be a new rc candidate soon.
Hope that helps.
thanks
mahadev
===
This issue is fixed with Eric's patch for HADOOP-7356. Since Owen is out on
vacation Iam working on
Reporter: Mahadev konar
Assignee: Mahadev konar
Priority: Minor
Fix For: 0.23.0
HADOOP-6929 allowed to make implementations/providers of SecurityInfo to be
configurable via service class loaders. For adding Security to TunnelProtocols
Unsubscribe.
Unsubscribe.
Gianmarco,
The issue I think is that if the jira is in progress it can only be marked
OPEN/Patch available by the person who is assigned the jira. I just tried
assigning the jira to myself, clicking on ³stop progress² and then
unassigning it.
You should be able to submit a patch and mark is
[
https://issues.apache.org/jira/browse/HADOOP-6646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mahadev konar resolved HADOOP-6646.
---
Resolution: Fixed
Hadoop Flags: [Reviewed]
I just committed this.
I only moved
Issue Type: Improvement
Reporter: Mahadev konar
Assignee: Mahadev konar
Fix For: 0.22.0
A liststatus call on a directory in hadoop archives leads to ( 2* number of
files in directory) open calls to the namenode. This is very sub optimal and
needs
18 matches
Mail list logo