You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shawn Heisey (JIRA)" <ji...@apache.org> on 2018/05/21 21:45:00 UTC

[jira] [Resolved] (SOLR-12382) new data not seen immediately after commit() on SolrCloud collection with only TLOG and PULL replicas

     [ https://issues.apache.org/jira/browse/SOLR-12382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shawn Heisey resolved SOLR-12382.
---------------------------------
    Resolution: Invalid

Problems like this are rarely bugs.  More likely that there is a reason commits are taking a long time, such as a configuration problem or insufficient system resources.

This issue tracker is not a support portal.  We have mailing lists and an IRC channel which should be used to discuss all problems before opening an issue.

http://lucene.apache.org/solr/community.html#mailing-lists-irc

Info we're going to want when you do get to the mailing list or the IRC channel: A solr.log file that includes a commit and the subsequent queries, with information about what documents were sent to the update handler, and the query details.  The full solrconfig.xml file would also be useful.

If it turns out there actually is a bug, we can re-open this issue.

> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org