[
https://issues.apache.org/jira/browse/RANGER-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16300289#comment-16300289
]
Kevin Risden commented on RANGER-1938:
--------------------------------------
The reason I went with changing all to DocValues is because Solr did this in
Solr 6.0 by default. See SOLR-8740 for details. Solr 5.5 has support for
DocValues. Solr 6.0 was just the first major version where the default was
changed. Moving to default DocValues=true matches closer to later versions of
Solr.
Do you still want a comment in there?
> 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: Improvement
> 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
> Assignee: Kevin Risden
> Labels: performance
> Fix For: 1.0.0, 0.7.2
>
> Attachments:
> 0001-RANGER-1938-Enable-DocValues-for-more-fields-in-Solr.patch
>
>
> 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
(v6.4.14#64029)
