Member since
06-02-2014
17
Posts
1
Kudos Received
2
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1808 | 04-28-2015 09:08 AM | |
1259 | 06-19-2014 12:59 PM |
09-09-2017
12:28 AM
How to point namenode particular txid ?
... View more
09-08-2017
01:16 AM
I was able to make the job run by adding hive-exec jar in HADOOP_CLASSPATH as well as adding the jar in distributed cache. Can you throw some light as to why do we need to export the jar to classpath and also add in distributed cache.
... View more
05-26-2015
06:43 PM
Thank you, mfox. My problem was that the basic install set all of HDFS's groups to "superuser" instead of "hadoop". Changing it to "hadoop" allowed mapreduce to write its history logs to the correct location.
... View more
05-12-2015
07:57 PM
The link to the source is here https://github.com/cloudera/hadoop-common/blob/cdh5.4.0-release/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/shell/FsUsage.java#L120
... View more
04-28-2015
09:08 AM
This turned out to be a configuration setting issue. "dfs.namenode.shared.edits.dir" had a directory value in it, and needed to be cleared.
... View more
06-19-2014
12:59 PM
This turned out to be an issue with speculative execution. (e.g. conf.set("mapred.map.tasks.speculative.execution", "false"); ) It was causing the job to create a new task before the previous task had cleaned up after itself. It turns out that MultipleOutputs doesn't handle speculative execution very well.
... View more