Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E13CE200BF7 for ; Mon, 9 Jan 2017 09:27:59 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id DFEC7160B3E; Mon, 9 Jan 2017 08:27:59 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 357BE160B3B for ; Mon, 9 Jan 2017 09:27:59 +0100 (CET) Received: (qmail 41493 invoked by uid 500); 9 Jan 2017 08:27:58 -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 41483 invoked by uid 99); 9 Jan 2017 08:27:58 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Jan 2017 08:27:58 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 545EA2C03DC for ; Mon, 9 Jan 2017 08:27:58 +0000 (UTC) Date: Mon, 9 Jan 2017 08:27:58 +0000 (UTC) From: "Prasanth Jayachandran (JIRA)" To: issues@hive.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HIVE-15565) LLAP: GroupByOperator flushes hash table too frequently MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 09 Jan 2017 08:28:00 -0000 [ https://issues.apache.org/jira/browse/HIVE-15565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15811045#comment-15811045 ] Prasanth Jayachandran commented on HIVE-15565: ---------------------------------------------- For LLAP, GBY hashtable memory should be shared by all executors. The problem is with tracking memory usage per thread. There is already an open jira for this. HIVE-15508 Ideally, we want to track memory usage per executor and flush based on usage vs max memory available per executor ratio. > LLAP: GroupByOperator flushes hash table too frequently > ------------------------------------------------------- > > Key: HIVE-15565 > URL: https://issues.apache.org/jira/browse/HIVE-15565 > Project: Hive > Issue Type: Bug > Components: llap > Reporter: Rajesh Balamohan > Assignee: Rajesh Balamohan > Priority: Minor > Attachments: HIVE-15565.1.patch > > > {{GroupByOperator::isTez}} would be true in LLAP mode. Current memory computations can go wrong with {{isTez}} checks in {{GroupByOperator}}. For e.g, in a LLAP instance with Xmx128G and 12 executors, it would start flushing hash table for every record once it reaches around 42GB (hive.tez.container.size=7100, hive.map.aggr.hash.percentmemory=0.5). > {noformat} > 2017-01-08T23:40:21,339 INFO [TezTaskRunner (1480722417364_1922_7_03_000004_1)] org.apache.hadoop.hive.ql.exec.GroupByOperator: Hash Table flushed: new size = 0 > 2017-01-08T23:40:21,339 INFO [TezTaskRunner (1480722417364_1922_7_03_000012_1)] org.apache.hadoop.hive.ql.exec.GroupByOperator: Hash Table flushed: new size = 0 > 2017-01-08T23:40:21,339 INFO [TezTaskRunner (1480722417364_1922_7_03_000004_1)] org.apache.hadoop.hive.ql.exec.GroupByOperator: Hash Tbl flush: #hash table = 1 > 2017-01-08T23:40:21,339 INFO [TezTaskRunner (1480722417364_1922_7_03_000012_1)] org.apache.hadoop.hive.ql.exec.GroupByOperator: Hash Tbl flush: #hash table = 1 > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)