[ 
https://issues.apache.org/jira/browse/SOLR-7133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329918#comment-14329918
 ] 

Shawn Heisey commented on SOLR-7133:
------------------------------------

bq. INFO  org.apache.solr.update.UpdateHandler    start 
commit{,optimize=false,openSearcher=false,waitSearcher=true,expungeDeletes=false,softCommit=false,prepareCommit=false}

Notice in that log line that it says "openSearcher=false" ?  A new searcher has 
not been opened, so the original searcher will be used for searches, and it is 
not aware of the new segments created by the updates and the commit.  Adding 
autoSoftCommit to the config as well as autoCommit should solve this problem, 
but if you want all of the updates in a particular batch to be done before the 
changes are visible, then it might not be the right thing to do.

I bet that your autoCommit setting which has a maxTime of 15000 also has 
openSearcher set to false.  With this config, you will never see your new 
documents unless your update process sends an explicit commit with 
openSearcher=true, or you restart Solr.

I don't know what to say about the flume batchDurationMillis setting.  You will 
need to find a support venue for flume.

http://flume.apache.org/mailinglists.html

If you want to continue this discussion about Solr, please use the mailing list 
or IRC.  This issue tracker is not the correct place.

http://lucene.apache.org/solr/resources.html#community


> 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]

Reply via email to