Hi Guo,
Can you please let me know if there was any specific configuration needed
to get Gridmix working with YARN+MRv2. We are getting the following
exception:
INFO gridmix.JobSubmitter: Job org.apache.hadoop.mapreduce.Job@18a8ce2
submission failed java.lang.ArithmeticException: / by zero
at
Hi Brian, I'm using hadoop-2.3.0-cdh5.1.0, there is gridmix jar in this
package.
step 1: using Rumen to generate the job trace file.
sudo -u yarn java -cp `hadoop classpath`
org.apache.hadoop.tools.rumen.TraceBuilder
file:///tmp/jobhistory_log/job-trace.json
Jason Lowe created MAPREDUCE-6021:
-
Summary: MR AM should add working directory to LD_LIBRARY_PATH
Key: MAPREDUCE-6021
URL: https://issues.apache.org/jira/browse/MAPREDUCE-6021
Project: Hadoop
Folks,
I think we are very close to voting on RC0. Just wanted to check one
(hopefully) last thing.
I am unable to verify the signed maven artifacts are actually deployed. To
deploy the artifacts, I did the following and it looked like it ran fine.
1. .m2/settings.xml - server-id is
Jason Lowe created MAPREDUCE-6022:
-
Summary: map_input_file is missing from streaming job environment
Key: MAPREDUCE-6022
URL: https://issues.apache.org/jira/browse/MAPREDUCE-6022
Project: Hadoop
Hi folks,
I have put together a release candidate (rc0) for Hadoop 2.5.0.
The RC is available at: http://people.apache.org/~kasha/hadoop-2.5.0-RC0/
The RC tag in svn is here:
https://svn.apache.org/repos/asf/hadoop/common/tags/release-2.5.0-rc0/
The maven artifacts are staged at
I am obviously a +1 (non-binding).
I brought a pseudo-distributed cluster and ran a few HDFS commands and MR
jobs.
On Fri, Aug 1, 2014 at 4:16 PM, Karthik Kambatla ka...@cloudera.com wrote:
Hi folks,
I have put together a release candidate (rc0) for Hadoop 2.5.0.
The RC is available at:
Hi folks,
From what I hear, a lot of devs use the git mirror for development/reviews
and use subversion primarily for checking code in. I was wondering if it
would make more sense just to move to git. In addition to subjective liking
of git, I see the following advantages in our workflow:
1.
Tom White helped me figure it out, and closed the Nexus repository for me.
Thanks Tom for helping and Stack for offering to help.
On Fri, Aug 1, 2014 at 11:28 AM, Karthik Kambatla ka...@cloudera.com
wrote:
Folks,
I think we are very close to voting on RC0. Just wanted to check one
Missed Andrew's email in the other thread. Looks like we might need
HDFS-6793.
I ll wait to see if others find any other issues, so I can address them all
together.
On Fri, Aug 1, 2014 at 4:25 PM, Karthik Kambatla ka...@cloudera.com wrote:
I am obviously a +1 (non-binding).
I brought a
Thanks for starting this thread Karthik! Big +1 from me. I only use svn
when I have to commit things or work on the site, otherwise it's always the
git mirror or local git repos.
Considering that the git mirror works as well as it does, I'd expect this
to be a pretty smooth transition.
Best,
+1, we did it for Oozie a while back and was painless with minor issues in
Jenkins jobs
Rebasing feature branches on latest trunk may be tricky as that may require
a force push and if I'm not mistaken force pushes are disabled in Apache
GIT.
thx
On Fri, Aug 1, 2014 at 4:43 PM, Karthik Kambatla
12 matches
Mail list logo
