[
https://issues.apache.org/jira/browse/HIVE-15017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15601270#comment-15601270
]
Alexandre Linte commented on HIVE-15017:
----------------------------------------
Which logs do you need in DEBUG mode? (Hadoop, Hive)
I added the hive-site.xml to help.
The HADOOP_YARN_HOME env variable is properly set on every datanode. I checked.
There is no "yarn.nodemanager.linux-container-executor.path" property set on
any of Hadoop configuration files. The default value must be used.
Yes, bin/container-executor is under Yarn home. Is that wrong?
> Random job failures with MapReduce and Tez
> ------------------------------------------
>
> Key: HIVE-15017
> URL: https://issues.apache.org/jira/browse/HIVE-15017
> Project: Hive
> Issue Type: Bug
> Components: Hive
> Affects Versions: 2.1.0
> Environment: Hadoop 2.7.2, Hive 2.1.0
> Reporter: Alexandre Linte
> Priority: Critical
> Attachments: hive_cli_mr.txt, hive_cli_tez.txt,
> nodemanager_logs_mr_job.txt, yarn_container_tez_job_datanode05.txt,
> yarn_container_tez_job_datanode06.txt, yarn_syslog_mr_job.txt,
> yarn_syslog_tez_job.txt
>
>
> Since Hive 2.1.0, we are facing a blocking issue on our cluster. All the jobs
> are failing randomly on mapreduce and tez as well.
> In both case, we don't have any ERROR or WARN message in the logs. You can
> find attached:
> - hive cli output errors
> - yarn logs for a tez and mapreduce job
> - nodemanager logs (mr only, we have the same logs with tez)
> Note: This issue doesn't exist with Pig jobs (mr + tez), Spark jobs (mr), so
> this cannot be an Hadoop / Yarn issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
