[
https://issues.apache.org/jira/browse/SOLR-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561778#comment-13561778
]
Mark Miller commented on SOLR-4343:
-----------------------------------
bq. but a few OOMs on the replica.
OOM's will pretty much screw you. Best thing to do is to pass the command line
arg when starting the vm that lets you run an arbitrary command on OOM - then
in that cmd you kill the process, log the problem - then if the process is not
supervised, start it again.
Try giving it more RAM.
> 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]
