ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Risden (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (RANGER-1938) Solr for Audit setup doesn't use DocValues effectively
Date Tue, 19 Dec 2017 22:11:00 GMT

     [ https://issues.apache.org/jira/browse/RANGER-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kevin Risden updated RANGER-1938:
    Summary: Solr for Audit setup doesn't use DocValues effectively  (was: Solr for Audit
setup doesn't require DocValues)

> Solr for Audit setup doesn't use DocValues effectively
> ------------------------------------------------------
>                 Key: RANGER-1938
>                 URL: https://issues.apache.org/jira/browse/RANGER-1938
>             Project: Ranger
>          Issue Type: Bug
>          Components: audit
>    Affects Versions: 0.6.0, 0.7.0, 0.6.1, 0.6.2, 0.6.3, 0.7.1
>            Reporter: Kevin Risden
> 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 noticed quite a few Ambari Infra
Solr OOM due to Ranger. I've talked with a few 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 reduced 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

This message was sent by Atlassian JIRA

View raw message