Data sent to Solr is not immediately searchable, nor do deletions take immediate effect. Like a database, changes must be committed. There are two types of commits:
Hard commit: This is expensive because it pushes the changes to the filesystem (making them persistent) and has a significant performance impact. This is performed by the
<autoCommit>
option insolrconfig.xml
or by addingcommit=true
request parameter to a Solr update URL.Soft commit: This is less expensive but is not persistent. This is performed by the
<autoSoftCommit>
option insolrconfig.xml
or using thesoftCommit=true
option along with thecommit
parameter or by using thecommitWithin
parameter.
The request to Solr could be the same request that contains data to be indexed then committed, or an empty request—it doesn't matter. For example, you can visit this URL to issue a commit on our mbreleases
core: http://localhost:8983/solr/mbreleases/update?commit=true...