rkirtir opened a new pull request, #4901:
URL: https://github.com/apache/hive/pull/4901

   
   
   ### What changes were proposed in this pull request?
   In the query-executor, we create ephemeral nodes which have the special 
behaviour that they are automatically deleted when the query-coordinator 
zookeeper client session is terminated. If there are no other Hive VWs on the 
cluster, sooner or later the entire path will be deleted.
   To avoid this, we need to have a persistent node on path 
/llap-sasl/user-hivefoo0/pnode0.
   
   ### Why are the changes needed?
   Hue or beeline session thows InvalidACL exception when executing drop 
database, drop table or alter table drop partition operations on a Hive Virtual 
Warehouse that is in Stopped state: 
"org.apache.zookeeper.KeeperException$InvalidACLException: KeeperErrorCode = 
InvalidACL for /llap-sasl/user-hive".
   The exception appears because the Hive VW wants to evict the cache in the 
LLAP executors, but those computes in a Stopped warehouse are not running.
   
   In the query-executor, we create ephemeral nodes which have the special 
behaviour that they are automatically deleted when the query-coordinator 
zookeeper client session is terminated. If there are no other Hive VWs on the 
cluster, sooner or later the entire path will be deleted.
   To avoid this, we need to have a persistent node on path.
   
   
   ### Does this PR introduce _any_ user-facing change?
   NO
   
   ### Is the change a dependency upgrade?
   NO
   
   
   ### How was this patch tested?
   Manually. This was tested on private cluster with crating data catalog and 
VWs and stopping VWS manually
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to