- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Killing HiveSessions with longer connection times
- Labels:
-
Apache Hive
Created 11-11-2016 05:46 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We have a requirement where, if there is any query which is taking up more time from HS2 session then terminate the connection and kill the job. To address this we have set below properties but we are seeing that jobs in YARN are not getting killed and running for more than two hours.
hive.server2.session.check.interval = 60000 (in ms) # 10 minutes hive.server2.idle.operation.timeout = 1800000 (in ms) # 30 minutes hive.server2.idle.session.timeout = 2400000 (in ms) # 40 minutes
Does setting below properties kill the related running YARN application after idle session time out. If not, is there any property which we need to set in HiveServer2 to kill long running queries.
Created 11-11-2016 12:56 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Even if session gets timedout, YARN will retry attempt upto 3 more times and application will get killed if all 4 attempts are failed. That might be the reason why your YARN application runs longer.
Please refer below thread for more information.
Created 11-11-2016 12:56 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Even if session gets timedout, YARN will retry attempt upto 3 more times and application will get killed if all 4 attempts are failed. That might be the reason why your YARN application runs longer.
Please refer below thread for more information.
Created 11-11-2016 05:49 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Kuldeep KulkarniThanks for your inputs,