You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Greg Senia (JIRA)" <ji...@apache.org> on 2017/03/07 19:56:37 UTC
[jira] [Updated] (RANGER-1429) Ranger Audit solrconfig.xml
optimizations
[ https://issues.apache.org/jira/browse/RANGER-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Greg Senia updated RANGER-1429:
-------------------------------
Attachment: RANGER-1429.patch
> Ranger Audit solrconfig.xml optimizations
> -----------------------------------------
>
> Key: RANGER-1429
> URL: https://issues.apache.org/jira/browse/RANGER-1429
> Project: Ranger
> Issue Type: Bug
> Components: audit
> Affects Versions: 0.7.0
> Reporter: Greg Senia
> Attachments: RANGER-1429.patch
>
>
> When using SolrCloud and having a single shard single replica with a large number of audit records 20GB for 2 weeks. It takes Solr a very long time to open up the replica for work. After doing some research I determine via thread dumps that on the first request to the Solr Collection it kicks off a Suggestion thread and a SpellCheck thread. I propose removing these as it does not seem to impact RangerAudit and solves the issue of Solr ranger_audits collection being unavailable after solr startup.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)