You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2017/11/17 20:30:00 UTC
[jira] [Created] (HIVE-18097) query move phase 2 - oversubscribing
the destination pool
Sergey Shelukhin created HIVE-18097:
---------------------------------------
Summary: query move phase 2 - oversubscribing the destination pool
Key: HIVE-18097
URL: https://issues.apache.org/jira/browse/HIVE-18097
Project: Hive
Issue Type: Sub-task
Reporter: Sergey Shelukhin
Final design TBD.
We may add an option to the trigger: "on full kill/ignore/delay kill".
The former will kill the query if the dest is full.
The ignore one would not perform the move... The thinking is that admin would add another trigger to kill queries after some time (e.g. - move after 10s, kill after 30s), and thus give slow/large queries a grace period in case dest is full so they cannot gracefully release the capacity.
It's possible to add a third option - "delay kill", where we would ignore the move, but kill the query if someone requests capacity and the pool is full.
Note that none of these requires oversubscription which is a pain to track.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)