[
https://issues.apache.org/jira/browse/SOLR-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14171207#comment-14171207
]
Peter Keegan commented on SOLR-6326:
------------------------------------
Mikhail Khludnev : not annoying at all, I think your questions and comments are
helpful.
I'm doing the indexing and commits with CloudSolrServer. The commit will block
until all replicas have successfully committed. After the commit, I could then
hit the ReloadCacheRequestHandlers, but wouldn't that open a new searcher twice
(assuming the commit resulted in a new searcher, too)?
Replacing EFF with DocValues does seem to be a much better way to handle rapid
field changes. It does seem risky, though, but I'll definitely look into it -
thanks.
> ExternalFileFieldReloader and commits
> -------------------------------------
>
> Key: SOLR-6326
> URL: https://issues.apache.org/jira/browse/SOLR-6326
> Project: Solr
> Issue Type: Bug
> Reporter: Peter Keegan
> Labels: difficulty-medium, externalfilefield, impact-medium
> Attachments: SOLR-6326.patch
>
>
> When there are multiple 'external file field' files available, Solr will
> reload the last one (lexicographically) with a commit, but only if changes
> were made to the index. Otherwise, it skips the reload and logs: "No
> uncommitted changes. Skipping IW.commit."
> IndexWriter.hasUncommittedChanges() returns false, but new external files
> should be reloaded with commits.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
