Return-Path: X-Original-To: apmail-hive-issues-archive@minotaur.apache.org Delivered-To: apmail-hive-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 77A57187B2 for ; Fri, 15 May 2015 20:18:00 +0000 (UTC) Received: (qmail 14274 invoked by uid 500); 15 May 2015 20:18:00 -0000 Delivered-To: apmail-hive-issues-archive@hive.apache.org Received: (qmail 14147 invoked by uid 500); 15 May 2015 20:18:00 -0000 Mailing-List: contact issues-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list issues@hive.apache.org Received: (qmail 13899 invoked by uid 99); 15 May 2015 20:17:59 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 May 2015 20:17:59 +0000 Date: Fri, 15 May 2015 20:17:59 +0000 (UTC) From: "Vaibhav Gumashta (JIRA)" To: issues@hive.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HIVE-10725) Better resource management in HiveServer2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HIVE-10725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vaibhav Gumashta updated HIVE-10725: ------------------------------------ Issue Type: Improvement (was: Bug) > Better resource management in HiveServer2 > ----------------------------------------- > > Key: HIVE-10725 > URL: https://issues.apache.org/jira/browse/HIVE-10725 > Project: Hive > Issue Type: Improvement > Components: HiveServer2, JDBC > Affects Versions: 1.3.0 > Reporter: Vaibhav Gumashta > Assignee: Vaibhav Gumashta > > We have various ways to control the number of queries that can be run on one HS2 instance (max threads, thread pool queuing etc). We also have ways to run multiple HS2 instances using dynamic service discovery. We should do a better job at: > 1. Monitoring resource utilization (sessions, ophandles, memory, threads etc). > 2. Being upfront to the client when we cannot accept new queries. > 3. Throttle among different server instances in case dynamic service discovery is used. > 4. Consolidate existing ways to control #queries into a simpler model. -- This message was sent by Atlassian JIRA (v6.3.4#6332)