BTW , my hadoop version is 2.3.0-cdh5.0.2
r7raul1...@163.com
From: Jeff Zhang
Date: 2015-06-29 13:23
To: user
Subject: Re: hive -e run tez query error
> But keeping that client cache disabled when running against trunk generally
> kills queries all the time with occasional errors like
> But keeping that client cache disabled when running against trunk generally
kills queries all the time with occasional errors like these.
I think tez staging directory is supposed to be deleted when JVM exit
(deleteOnExit), why killing query will cause the path deleted ?
On Sat, Jun 27, 2015
> perhaps deleteOnExit() is set somewhere
fs.cache.disable settings from hdfs-site.xml are usually to blame for that.
Till hive-1.0, HiveServer2 used to leak filesystem objects, so the cache
was disabled.
> 2015-06-25 15:54:33,673 INFO FSNamesystem.audit: allowed=true
>ugi=lujian (auth:SIMPLE)
perhaps deleteOnExit() is set somewhere
From: Jeff Zhang mailto:zjf...@gmail.com>>
Reply-To: User mailto:user@hive.apache.org>>
Date: Thursday, June 25, 2015 at 2:09 AM
To: User mailto:user@hive.apache.org>>
Subject: Re: hive -e run tez query error
The drop table command bet
The drop table command between these 2 query fails due to permission issue.
If I solve the permission issue, the tez error will disappear.
But what confuse me is that I suppose the failure of drop table command
should not affect the following tez jobs. But from the hdfs-audit logs,
tez_staging_dir
Sorry , I made a mistake,
use hivecli to execute same query on tez ,throw the same exception.
r7raul1...@163.com
From: r7raul1...@163.com
Date: 2015-06-23 13:53
To: user
Subject: hive -e run tez query error
When I use hive 1.1.0 on tez 0.53 in hadoop 2.3.0:
hive -v -e "set hive.execution.engi
