All,
We have our server set to soft-commit every 30 seconds.
If we know we are going to be sending a lot of documents at once, if we
set "commitWithin" to something longer -- for those document-add/replace
requests, will that override the soft-commit setting, or will the
soft-commit setting just go-ahead and soft-commit regardless?
I'm assuming that the global soft-commit will simply happen since the
documents are all going to the same place.
Given that we use Solr as an online index (meaning that we are
constantly adding small numbers of documents to a comparatively large
index), would it make more sense for us to:
1. Disable global soft-commit
2. Change our "document-add" operations to always specify commitWithin=30s
Doing steps 1-2 above seems like it would give us more control over
processes where we know we are going to be adding lots of documents, and
we can speed-up that indexing operation. It would also guarantee that we
get a fairly up-to-date index to search while NOT committing after
adding every single document (which I understand to be a horrible
practice for performance).
We are currently using Solr 7.7, if that distinction is important. (For
example, if commitWithin requires 8.x or later, or something like that.)
Thanks,
-chris
