[
https://issues.apache.org/jira/browse/SOLR-12382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16483188#comment-16483188
]
Mark Miller commented on SOLR-12382:
------------------------------------
Whoever added the feature will be able to comment better, but from what I have
seen, non leader replicas skip any commit with tlog mode - and only in tests,
rather then just returning on commit, there is an assert that tries to wait
until the replica appears to be in sync with the leader.
Pull replicas also seem to just skip any commit on replicas and log a warning -
they don't have the test wait code. In both cases, I don't see how
waitSearcher=true would affect anything on the replica side unless somehow it's
handled in some strange other place. AFAICT it would only wait for the leader
to open the new searcher.
> new data not seen immediately after commit() on SolrCloud collection with
> only TLOG and PULL replicas
> -----------------------------------------------------------------------------------------------------
>
> Key: SOLR-12382
> URL: https://issues.apache.org/jira/browse/SOLR-12382
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 7.3
> Environment: SolrCloud on Amazon Linux AMI 2018.03
>
> Reporter: Nguyen Nguyen
> Priority: Major
>
> On collection with TLOG/PULL replicas, queries that follow right after
> commit(waitSearch:true) would NOT return newly added data until several
> seconds later.
> Tested same scenario on another collection with only NRT replicas and found
> that it behaved as expected (query returned newly added data right after
> commit(waitSearch:true) was called.
> 7.3 SolrCloud with 3 shards, each shard has 2 TLOG replicas + 1 PULL replica
> Commit settings
> <autoCommit>
> <maxTime>15000</maxTime>
> <openSearcher>false</openSearcher>
> </autoCommit>
> <autoSoftCommit>
> <maxTime>-1</maxTime>
> </autoSoftCommit>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
