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 EA15A200D61 for ; Tue, 19 Dec 2017 22:58:22 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id E87F7160C1B; Tue, 19 Dec 2017 21:58:22 +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 3BE80160BFF for ; Tue, 19 Dec 2017 22:58:22 +0100 (CET) Received: (qmail 76789 invoked by uid 500); 19 Dec 2017 21:58:21 -0000 Mailing-List: contact dev-help@ranger.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ranger.apache.org Delivered-To: mailing list dev@ranger.apache.org Received: (qmail 76778 invoked by uid 99); 19 Dec 2017 21:58:21 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Dec 2017 21:58:21 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id B6E801A0B1F for ; Tue, 19 Dec 2017 21:58:20 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.299 X-Spam-Level: * X-Spam-Status: No, score=1.299 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 72xBHyrqR3XA for ; Tue, 19 Dec 2017 21:58:19 +0000 (UTC) Received: from us-smtp-delivery-102.mimecast.com (us-smtp-delivery-102.mimecast.com [216.205.24.102]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id E3D0A5F39E for ; Tue, 19 Dec 2017 21:58:18 +0000 (UTC) Received: from MBX080-W2-CO-4.exch080.serverpod.net (out.exch080.serverdata.net [199.193.207.80]) (Using TLS) by us-smtp-1.mimecast.com with ESMTP id us-mta-191-xhNxE1jBOsKSNSBOwaLcwQ-1; Tue, 19 Dec 2017 16:58:17 -0500 Received: from MBX080-W3-CO-5.exch080.serverpod.net (10.224.117.160) by MBX080-W3-CO-3.exch080.serverpod.net (10.224.117.156) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 19 Dec 2017 13:58:16 -0800 Received: from MBX080-W3-CO-5.exch080.serverpod.net ([10.224.117.160]) by MBX080-W3-CO-5.exch080.serverpod.net ([10.224.117.160]) with mapi id 15.00.1263.000; Tue, 19 Dec 2017 13:58:16 -0800 From: Velmurugan Periasamy To: "user@ranger.apache.org" CC: "dev@ranger.apache.org" Subject: Re: Ranger and Ambari Infra Solr (or another Solr install) - OOM Thread-Topic: Ranger and Ambari Infra Solr (or another Solr install) - OOM Thread-Index: AQHTeRO8wGjGU3dIukW0sjvO0SarxqNLaRAA Date: Tue, 19 Dec 2017 21:58:15 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-source-routing-agent: Processed MIME-Version: 1.0 X-MC-Unique: xhNxE1jBOsKSNSBOwaLcwQ-1 Content-Type: multipart/alternative; boundary="_000_D65EF5332ADDC4vperiasamyhortonworkscom_" archived-at: Tue, 19 Dec 2017 21:58:23 -0000 --_000_D65EF5332ADDC4vperiasamyhortonworkscom_ Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable This is a good idea. Thanks Kevin. Please go ahead with JIRA. Adding dev li= st. From: Kevin Risden > Reply-To: "user@ranger.apache.org" > Date: Tuesday, December 19, 2017 at 4:52 PM To: "user@ranger.apache.org" > Subject: Ranger and Ambari Infra Solr (or another Solr install) - OOM Ranger uses Ambari Infra Solr (or another Apache Solr install) for storing = Ranger Audit events for displaying in Ranger Admin. In our case, we have no= ticed quite a few Ambari Infra Solr OOM due to Ranger. I've talked with a f= ew other people who are having very similar problems with OOM errors. I've typed up some details about how the way Ranger is using Solr requires = a lot of heap. I've also outlined the fix for this which significantly redu= ced the amount of heap memory required. I'm an Apache Lucene/Solr committer= so this optimization/usage might not be immediately obvious to those using= Solr especially version 5.x. https://risdenk.github.io/2017/12/18/ambari-infra-solr-ranger.html I can open a JIRA issue if this would be helpful to fix the managed-schema = shipped with Ranger. This would also be something that should be fixed upst= ream with Ambari if possible when deploying Ranger and Ambari Infra Solr. Kevin Risden --_000_D65EF5332ADDC4vperiasamyhortonworkscom_--