[
https://issues.apache.org/jira/browse/SOLR-12382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16483416#comment-16483416
]
Cao Manh Dat commented on SOLR-12382:
-------------------------------------
bq. Right, I believe that is the idea - they catch up when they end up polling.
So I assume this is all by design. Would be nice to at least optionally get the
behavior of waiting until replicas are up to date before return from a commit
w/ waitSearcher=true.
(y) Totally correct, nothing more need to be explained here.
> 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]
