I have HIVE working with TEZ, and the results come out smoothly.
When I look at the TEZ view, the query ran successfully:
But when I check YARN, the job is still there, running and consuming my resources:
Can anyone provide hints on what to look for here?
TEZ initializes session when we run some hive job and based on the tez configurations we will have one YARN application initialized (as you can see in the Resource manager).
The TEZ session will be same for all the queries that we are running until the session gets closed,
In TEZ view we can see same application id for all the queries that we are running in Hive but DAG_ID will be different for all.
In case of MapReduce we are not going to hold any of the resources like TEZ but we are going to run seperate applications for each query.
If the answer is helpful to resolve the issue, Login and Click on Accept button below to close this thread.This will help other community users to find answers quickly :-)
Is there a way so that new queries are executed through this previous TEZ application rather than generating new ones stucked on `ACCEPTED`? (for it is very annoying to have to kill the previous each time I want to run something new)