You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Kevin Risden (JIRA)" <ji...@apache.org> on 2017/12/21 17:09:00 UTC
[jira] [Commented] (AMBARI-22684) Ambari Infra Solr should use
DocValues by default
[ https://issues.apache.org/jira/browse/AMBARI-22684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16300294#comment-16300294 ]
Kevin Risden commented on AMBARI-22684:
---------------------------------------
RANGER-1938 is the same issue to fix in the Ranger project. This ticket is to fix this for all Ambari Infra Solr deployments.
> Ambari Infra Solr should use DocValues by default
> -------------------------------------------------
>
> Key: AMBARI-22684
> URL: https://issues.apache.org/jira/browse/AMBARI-22684
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-infra
> Affects Versions: 2.4.0, 2.5.0, 2.6.0
> 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
(v6.4.14#64029)