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 E0DDB2004F5 for ; Sat, 12 Aug 2017 01:31:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id DF3C816E3C0; Fri, 11 Aug 2017 23:31:04 +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 3216516E3BD for ; Sat, 12 Aug 2017 01:31:04 +0200 (CEST) Received: (qmail 40890 invoked by uid 500); 11 Aug 2017 23:31:03 -0000 Mailing-List: contact dev-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 dev@hive.apache.org Received: (qmail 40875 invoked by uid 99); 11 Aug 2017 23:31:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Aug 2017 23:31:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 935F7C05F7 for ; Fri, 11 Aug 2017 23:31:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id PL5LKZg74teH for ; Fri, 11 Aug 2017 23:31:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 3D08E5F3D1 for ; Fri, 11 Aug 2017 23:31:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 79BE7E002C for ; Fri, 11 Aug 2017 23:31:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 331C523E7B for ; Fri, 11 Aug 2017 23:31:00 +0000 (UTC) Date: Fri, 11 Aug 2017 23:31:00 +0000 (UTC) From: "Prasanth Jayachandran (JIRA)" To: dev@hive.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HIVE-17304) ThreadMXBean based memory allocation monitory for hash table loader MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 11 Aug 2017 23:31:05 -0000 Prasanth Jayachandran created HIVE-17304: -------------------------------------------- Summary: ThreadMXBean based memory allocation monitory for hash table loader Key: HIVE-17304 URL: https://issues.apache.org/jira/browse/HIVE-17304 Project: Hive Issue Type: Bug Affects Versions: 3.0.0 Reporter: Prasanth Jayachandran Assignee: Prasanth Jayachandran Hash table memory monitoring is based on java data model which can be unreliable because of various reasons (wrong object size estimation, adding new variables to any class without accounting its size for memory monitoring, etc.). We can use allocation size per thread that is provided by ThreadMXBean and fallback to DataModel in case if JDK doesn't support thread based allocations. -- This message was sent by Atlassian JIRA (v6.4.14#64029)