[
https://issues.apache.org/jira/browse/SOLR-7133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329740#comment-14329740
]
Shawn Heisey commented on SOLR-7133:
------------------------------------
This should have been brought up on the mailing list first, rather than going
into the bug tracker.
If flume is not sending a commit (and Solr is not configured with relevant
autoCommit and/or autoSoftCommit settings), then any updates that have been
done will not be visible. Very likely flume has a way to send the commit, but
I have no experience with it, so I do not know where.
http://lucidworks.com/blog/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/
That article title says "SolrCloud" but the concepts are applicable to Solr in
general.
What I've found to be good autoCommit settings are: 1) autoCommit with a
maxTime of five to fifteen minutes and openSearcher set to false. 2)
autoSoftCommit with a maxTime that represents the most time you can stand to
wait for new documents to show up. I personally would not configure
autoSoftCommit with an interval shorter than one minute.
maxTime is in milliseconds, so five minutes is 300000.
> 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]
