[
https://issues.apache.org/jira/browse/AMBARI-17044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-17044:
----------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
committed to trunk:
{code:java}
commit bd71e62d3d5391e6413916da30fc1c309be3e607
Author: oleewere <oleew...@gmail.com>
Date: Mon Jun 13 16:54:28 2016 +0200
AMBARI-17144. Optimize LogSearch Solr for cache setting and default values
(Bosco Durai via oleewere)
{code}
committed to branch-2.4
{code:java}
commit afdbe49181b27b5c261c4d2a00e7489d47bf6faf
Author: oleewere <oleew...@gmail.com>
Date: Mon Jun 13 16:54:28 2016 +0200
AMBARI-17144. Optimize LogSearch Solr for cache setting and default values
(Bosco Durai via oleewere)
{code}
> Optimize LogSearch Solr for cache setting and default values
> ------------------------------------------------------------
>
> Key: AMBARI-17044
> URL: https://issues.apache.org/jira/browse/AMBARI-17044
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
> Affects Versions: 2.4.0
> Reporter: Don Bosco Durai
> Assignee: Don Bosco Durai
> Fix For: 2.4.0
>
>
> The default setting of Solr waits for the cache to warm up completely before
> servicing any request. In big environments with huge amount of logs,
> restarting of Solr will take a long time or intermittently will Solw down.
> Solr provides an option to make the cache available before it is fully
> warmed. This will provide more real-time performance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
