[
https://issues.apache.org/jira/browse/SOLR-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561411#comment-13561411
]
Joseph Dale commented on SOLR-4343:
-----------------------------------
This only happens on a database import using DIH. It almost seems as though the
last batch only commits on the leader. I will bring up my test environment in
the morning and grab the log output from all three servers while its happening.
> Solrcloud 4.1 inconsistent # of results in replicas
> ----------------------------------------------------
>
> Key: SOLR-4343
> URL: https://issues.apache.org/jira/browse/SOLR-4343
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.1
> Environment: Ubuntu12.04 / Java 1.7.11 / Tomcat7 / Zookeeper 3.4.5
> Reporter: Joseph Dale
> Priority: Critical
>
> I have a one shard collection, with one replica.
> I did a dataImport from my oracle DB.
> In the master, I have 93835 docs, in the non master 92627.
> I have tried http://machinename:8080/solr/collection/update/commit=true on
> the master, but the index does not replicate the replica.
> Also, the node list different generations of the core.
> I have left it alone for 2 hours and they never sync. Both nodes think that
> they are current, only on really is. I can reproduce this 100% of the time.
> -Joey
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
