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 D4403200CA3 for ; Thu, 18 May 2017 01:52:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D2BD9160BCD; Wed, 17 May 2017 23:52:08 +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 24F3B160BBA for ; Thu, 18 May 2017 01:52:07 +0200 (CEST) Received: (qmail 32028 invoked by uid 500); 17 May 2017 23:52:07 -0000 Mailing-List: contact issues-help@impala.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@impala.incubator.apache.org Delivered-To: mailing list issues@impala.incubator.apache.org Received: (qmail 32018 invoked by uid 99); 17 May 2017 23:52:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 May 2017 23:52:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id C9383180692 for ; Wed, 17 May 2017 23:52:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.001 X-Spam-Level: X-Spam-Status: No, score=-100.001 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id BdyjE02bjiw1 for ; Wed, 17 May 2017 23:52:06 +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 58E205FE3B for ; Wed, 17 May 2017 23:52:05 +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 B6F24E015A for ; Wed, 17 May 2017 23:52:04 +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 5279F2193C for ; Wed, 17 May 2017 23:52:04 +0000 (UTC) Date: Wed, 17 May 2017 23:52:04 +0000 (UTC) From: "Matthew Jacobs (JIRA)" To: issues@impala.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (IMPALA-5301) minicluster kudu needs mem limits set MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 17 May 2017 23:52:09 -0000 [ https://issues.apache.org/jira/browse/IMPALA-5301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew Jacobs resolved IMPALA-5301. ------------------------------------ Resolution: Fixed Fix Version/s: Impala 2.9.0 commit d04f96b990c18ed17c82c0151978b56f936f0574 Author: Matthew Jacobs Date: Wed May 10 11:10:21 2017 -0700 IMPALA-5301: Set Kudu minicluster memory limit By default, Kudu assumes it has 80% of system memory which is far too high for the minicluster. This sets a mem limit of 2gb and lowers the limit of the block cache. These values were tested on a gerrit-verify-dryrun job as well as an exhaustive run. This patch also simplifies TestKuduMemLimits which was unnecessarily creating a large table during test execution. Change-Id: I7fd7e1cd9dc781aaa672a2c68c845cb57ec885d5 Reviewed-on: http://gerrit.cloudera.org:8080/6844 Reviewed-by: Todd Lipcon Reviewed-by: Tim Armstrong Tested-by: Impala Public Jenkins > minicluster kudu needs mem limits set > ------------------------------------- > > Key: IMPALA-5301 > URL: https://issues.apache.org/jira/browse/IMPALA-5301 > Project: IMPALA > Issue Type: Improvement > Components: Infrastructure > Affects Versions: Impala 2.8.0 > Reporter: Matthew Jacobs > Labels: kudu > Fix For: Impala 2.9.0 > > > The minicluster runs Kudu without an explicit memory limit, and Kudu defaults to assuming it can use 80% of system memory. We should set a limit to avoid overcommitting system memory. > We need to keep the value low because aws test nodes (jenkins.impala.io) are small, see IMPALA-5297. I tested a limit of 1gb but that wasn't enough -- TestKuduMemLimits failed. We may try something a bit larger, or perhaps find other ways to reduce the requirements of minicluster tests. -- This message was sent by Atlassian JIRA (v6.3.15#6346)