[
https://issues.apache.org/jira/browse/SOLR-7133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332279#comment-14332279
]
Shawn Heisey commented on SOLR-7133:
------------------------------------
That's an *example config* -- specifically for autoCommit. Solr itself
defaults to openSearcher=true when you send a commit to the update handler, or
if you do not specify openSearcher on the autoCommit config.
Since 4.0, we strongly recommend using openSearcher=false with autoCommit. The
idea behind that recommendation is that Solr will automatically do commits that
start new transaction logs but it will not automatically make new documents
visible. There are other mechanisms for document visibility.
If you want to automatically do commits for document visibility, you have two
choices: use autoSoftCommit, or use the commitWithin parameter on your update
requests. You always have the option of making your application entirely
responsible for document visibility by sending manual soft commits. It can do
hard commits too, but if you have autoCommit, there's no reason to do the more
expensive hard commits.
Because this is not a bug and I've covered all the important discussion points
about commits, I will offer no more advice here. Use the mailing list or the
IRC channel. I am present on both.
> Solr is required to be restarted after updating with flume
> ----------------------------------------------------------
>
> Key: SOLR-7133
> URL: https://issues.apache.org/jira/browse/SOLR-7133
> Project: Solr
> Issue Type: Bug
> Components: Data-driven Schema
> Affects Versions: 4.10.3
> Environment: Oracle Linux 6.6
> solr 4.10.3
> flume-1.4.0
> Reporter: DeepakVohra
>
> After updating Solr with Flume the Solr is required to be restarted before
> the updates get listed with /select query. Shouldn't the updates get listed
> with /select query without restarting Solr as with updating from the Solr
> Admin Console?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
