On 6/7/2018 12:10 PM, Moenieb Davids wrote:
> Challenges:
> When performing full text searches without concurrently executing updates,
> solr seems to be doing well. Running updates also does okish given the
> nature of the transaction. However, when I run search and updates
> simultaneously, perfo
Hi,
It is also likely that your indexing is using resources and that there are not
enough resources for queries to process. Indexing can put stress on heap and
GCs might be slowing Solr down resulting in observed latency. Can you tell us a
bit more on size of your index, server configs, heap siz
And in solrconfig.xml, it is possible to configure the searches to warm the
index up before the users see it.
Regards,
Alex
On Thu, Jun 7, 2018, 21:27 David Hastings,
wrote:
> When you are sending updates you are adjusting the segments which take them
> out of memory and the index becomes "
When you are sending updates you are adjusting the segments which take them
out of memory and the index becomes "cold" until it gets enough searches to
cache the various aspects of the index.
On Thu, Jun 7, 2018 at 2:10 PM, Moenieb Davids
wrote:
> Hi All,
>
> Background:
> I am currently testing
Hi All,
Background:
I am currently testing a deployment of a content management framework where
I am trying to punt Solr as the tool of choice for ingestion and searching.
Current status:
I have deployed SolrCloud across multiple servers with multiple shards and
a replication factor of 2.
In term
