[
https://issues.apache.org/jira/browse/SOLR-16856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17742544#comment-17742544
]
Tomas Eduardo Fernandez Lobbe commented on SOLR-16856:
------------------------------------------------------
I saw many people very confused when starting to use Solr because the documents
didn't show up in search (sometimes after struggling with other unrelated
issues that also caused docs not to show up, like auth, bad endpoints, bad
schema, etc). While I understand David's point, I still believe having docs
eventually show up is a better getting-started experience. Users will
eventually have to learn the commit/auto-commit concepts, but I believe it's
much better for them to learn it while investigating the NRT-ness (maybe after
asking "why are docs taking so long to show up?") than on their initial setup.
> Use autoSoftCommit with the default configSet
> ---------------------------------------------
>
> Key: SOLR-16856
> URL: https://issues.apache.org/jira/browse/SOLR-16856
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Houston Putman
> Priority: Major
> Fix For: 9.3
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The default autoCommit/autoSoftCommit settings that ship with Solr's default
> configSet are listed as such:
>
> <autoCommit>
> <maxTime>${solr.autoCommit.maxTime:15000}</maxTime>
> <openSearcher>false</openSearcher>
> </autoCommit>
> <autoSoftCommit>
> <maxTime>${solr.autoSoftCommit.maxTime:-1}</maxTime>
> </autoSoftCommit>
>
> With "openSearcher" set to false on the autoCommit, and no autoSoftCommit
> being used, there is little guarantee as to when users can expect to see
> their documents returned from Solr.
>
> We should use a pretty NRT-ish number for the default autoSoftCommit, like
> 3000.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]