Failing because I am unlikely to write too排查方案

tez本身不带logs，我在输入hive的时候碰到了下面的报错

Logging initialized using configuration in file:/home/appleyuchi/bigdata/apache-hive-3.0.0-bin/conf/hive-log4j2.properties Async: true
Exception in thread "main" java.lang.RuntimeException: java.io.IOException: Previous writer likely failed to write hdfs://Desktop:9000/tmp/hive/appleyuchi/_tez_session_dir/b334822e-6e45-45c9-9788-7aac05961286-resources/*. Failing because I am unlikely to write too.at org.apache.hadoop.hive.ql.session.SessionState.start(SessionState.java:676)at org.apache.hadoop.hive.ql.session.SessionState.beginStart(SessionState.java:585)at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:747)at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:683)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:498)at org.apache.hadoop.util.RunJar.run(RunJar.java:318)at org.apache.hadoop.util.RunJar.main(RunJar.java:232)
Caused by: java.io.IOException: Previous writer likely failed to write hdfs://Desktop:9000/tmp/hive/appleyuchi/_tez_session_dir/b334822e-6e45-45c9-9788-7aac05961286-resources/*. Failing because I am unlikely to write too.at org.apache.hadoop.hive.ql.exec.tez.DagUtils.localizeResource(DagUtils.java:1191)at org.apache.hadoop.hive.ql.exec.tez.DagUtils.addTempResources(DagUtils.java:1042)at org.apache.hadoop.hive.ql.exec.tez.DagUtils.localizeTempFilesFromConf(DagUtils.java:931)at org.apache.hadoop.hive.ql.exec.tez.TezSessionState.ensureLocalResources(TezSessionState.java:587)at org.apache.hadoop.hive.ql.exec.tez.TezSessionState.openInternal(TezSessionState.java:279)at org.apache.hadoop.hive.ql.exec.tez.TezSessionState.beginOpen(TezSessionState.java:248)at org.apache.hadoop.hive.ql.session.SessionState.start(SessionState.java:673)... 9 more

$HIVE_HOME/logs/hive.log会汇报关于tez的详细错误:

报错	解决方案
ERROR [main] common.FileUtils: The jar file path file:///home/appleyuchi/bigdata/hadoop-3.1.2/share/hadoop/common/hadoop-lzo-0.4.13.jar/home/appleyuchi/bigdata/apache-tez-0.9.2-bin/* doesn't exist	export HIVE_AUX_JARS_PATH=$HADOOP_HOME/share/hadoop/common/hadoop-lzo-0.4.13.jar$TEZ_JARS 改成 export HIVE_AUX_JARS_PATH=$HADOOP_HOME/share/hadoop/common/hadoop-lzo-0.4.13.jar:$TEZ_JARS
ERROR [main] common.FileUtils: The jar file path file:///home/appleyuchi/bigdata/apache-tez-0.9.2-bin/*	export TEZ_HOME=/home/appleyuchi/bigdata/apache-tez-0.9.2-bin export TEZ_CONF_DIR=$TEZ_HOME/conf export TEZ_JARS=$TEZ_HOME/:$TEZ_HOME/lib export HADOOP_CLASSPATH=$HADOOP_CLASSPATH:$TEZ_CONF_DIR:$TEZ_JARS export HIVE_AUX_JARS_PATH=$HADOOP_HOME/share/hadoop/common/hadoop-lzo-0.4.13.jar:$TEZ_JARS
Unexpected character '/' (code 47) in prolog; expected '<' ”.	/** xxxxx / 改成:* <!-- /** XXXXXx */ --> 讲人话就是tez-site.xml的开头官方说明用<></>注释掉
Caused by: com.ctc.wstx.exc.WstxParsingException: Illegal processing instruction target ("xml"); xml (case insensitive) is reserved by the specs. at [row,col,system-id]: [18,5,"file:/home/appleyuchi/bigdata/apache-tez-0.9.2-bin/conf/tez-site.xml"]	<?xml version="1.0"?> <?xml-stylesheet type="text/xsl" href="configuration.xsl"?> WARNING: THIS IS A GENERATED TEMPLATE PURELY FOR DOCUMENTATION PURPOSES AND SHOULD NOT BE USED AS A CONFIGURATION FILE FOR TEZ 这些全部注释掉即可
ERROR [main] tez.DagUtils: Could not find the jar that was being uploaded	???????这个我目前也没解决，尴尬了

调试的过程中发现，hive-env.sh与.bashrc中设置环境变量可以起到相同的效果。

总结:

终端报错Failing because I am unlikely to write too,其实是需要根据表格中的报错信息，逐个调试后，才能最终消除的。

Failing because I am unlikely to write too排查方案相关推荐

Hive引擎改为Tez笔记
环境: 组件版本 Hadoop 3.1.2 Hive 3.0.0 Tez 0.9.2 Zookeeper 3.6.0 Hbase 2.2.4 因为我采用了hbase表格映射到hive,所以和hbas ...
《docker基础篇：8.Docker常规安装简介》包括：docker常规安装总体步骤、安装tomcat、安装mysql、安装redis
文章目录 8.Docker常规安装简介 8.1 docker常规安装总体步骤 8.2安装tomcat 8.3 安装mysql 8.3.1 docker hub上面查找mysql镜像 8.3.2 从do ...
InnoDB: Failing assertion: trx-isolation_level == TRX_ISO_READ_UNCOMMITTED
最近再次碰到之前遇到的断言失败的bug,错误信息如下: InnoDB: Failing assertion: trx->isolation_level == TRX_ISO_READ_UNCOM ...
【异常】Container exited with a non-zero exit code 1 Failing this attempt.Stack trace: ExitCodeException
[异常]Container exited with a non-zero exit code 1 Failing this attempt.Stack trace: ExitCodeException ...
Attachments failing with invalid id (Bugtraker.net)
Attachments failing with invalid id (Bugtraker.net) Bugtracker.net 迁移到另外一台服务器后,在添加附件是出现配置情况: 源机器:w2k ...
【hadoop】java 获取 yarn app 信息报错 ConfiguredRMFailoverProxyProvider - Failing over to rm2
文章目录 1.概述 1.概述 java 获取 yarn app 信息报错 ConfiguredRMFailoverProxyProvider - Failing over to rm2 2022-0 ...
Consul小贴士-记一次Consul注册failing状态跟踪
前言最近抽了点时间基于最新的Consul1.0.2构建了集群,替换了原来的0.9.2服务.结果在启动基于SpringCloud D版的服务时所有节点的health状态均为DOWN,瞬间一切都不好了, ...
cephfs：1 clients failing to respond to cache pressure原因分析
问题现象 ceph -s中经常出现报警: 1 clients failing to respond to cache pressure 其大致原因是cephfs的mds让客户端释放部分metadata ...
Kafka消费异常报Failing OffsetCommit request since the consumer
目录前言排查与解决总结前言前段时间线上某个业务系统的Kafka消费端出现数据异常,一直在重复消费某个时间段内的数据,导致界面上重复数据越来越多,询问运维发现前几日有出现过一次网络波动,推测可 ...

Failing because I am unlikely to write too排查方案

Failing because I am unlikely to write too排查方案相关推荐

最新文章

热门文章