[
https://issues.apache.org/jira/browse/SOLR-3146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211918#comment-13211918
]
Yonik Seeley commented on SOLR-3146:
------------------------------------
So I've thought about changing to soft commits by default too. Here's the
issue:
People use commit to make their recent updates visible (and a NRT softCommit
would now be most appropriate).
But commit also flushes all segments to disk and syncs them, and in a
master-slave scenario causes index changes to be replicable.
One possibility is to add a softCommit default of true to the normal update
handlers.
People migrating an existing solrconfig wouldn't get that default, but new
users (or users starting from scratch with the new solrconfig would).
I don't know if it's worth it or not though. Thoughts?
> Create migration guide from 3.x to 4.0
> --------------------------------------
>
> Key: SOLR-3146
> URL: https://issues.apache.org/jira/browse/SOLR-3146
> Project: Solr
> Issue Type: Task
> Components: documentation
> Reporter: Jan Høydahl
> Fix For: 4.0
>
>
> Spinoff from SOLR-3141:
> {quote}
> Perhaps an official migration guide on the CMS would be helpful too when 4.0
> hits the road. Such a guide would be more in-depth than the upgrading notes
> in CHANGES. We could have a paragraph about optimize/forceMerge, and another
> paragraph about softCommit/commitWithin as preferred to explicit commit,
> which is also a huge mistake many people do, they do over-committing!
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
