Member since
09-06-2017
3
Posts
1
Kudos Received
0
Solutions
10-19-2017
12:23 PM
In our case, restarting Hive (or the entire stack for that matter) didn't seem to do anything. After playing with some resource allocation, we were able to get some jobs to go through, but the ones that were killed still remain. I'm starting to wonder if it's an issue with Tez not recognizing that jobs are being killed.
... View more
09-06-2017
03:38 PM
@Vinod Bonthu Sorry, updated post to reflect versions
... View more
09-06-2017
02:32 PM
1 Kudo
I have a Hive query (coming from Nifi), it is an insert operation, and Tez (view from Ambari) has reported it running for >48 hours. This was preventing other operations from occuring, so I wanted to kill the query so the backlog could be processed. I killed the associated Yarn Application. The Tez view from Ambari still shows the status as Running. Clicking through to the Application ID shows the status as Killed and Final Status as Undefined. Clicking through to the DAG shows the status as Killed, and the only listed Vertex is also Killed. Total Tasks for the DAG is 1. However, despite all this the query is still marked as running in TEZ and other queries are blocked behind it. Even non-modifying queries like a simple SELECT COUNT(*) are unable to run. This has persisted across Yarn, Hive, Tez, and even entire machine restarts.
Is there some way to kill off the operations that Tez is showing? Killing the yarn application doesn't seem to be sufficient. Versions: YARN: 2.7.3 Tez: 0.7.0 Hive: 1.2.1000
... View more
Labels:
- Labels:
-
Apache Hive
-
Apache Tez
-
Apache YARN