You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by 汤林 <ta...@126.com> on 2014/07/30 11:08:10 UTC
PeerSync: too many updates received since start - startingUpdates
no longer overlaps with our currentUpdates
Hi, All.
I met one issue when sending lots of docs to a 2-nodes SolrCloud. My env has one collection with 2 nodes. The only collection has 2 shards with 2 replica of each shard.
We are using Solr 4.7.
We found this warning when we are sending docs to the SolrCloud. And we noticed one request taking a quite long time without response, and we noticed this warning. After that warning, the solr node get into recovering state.
2014年7月25日 上午6:18:22
WARN
PeerSync
PeerSync: core=collection1_shard2_replica2 url=http://<ip2>:8080/solr too many updates received since start - startingUpdates no longer overlaps with our currentUpdates
And there is another issue during recovering, even if we restart the solr server. If we have commit in the good node (<ip1>:8080) , there are always errors and the index will be rebuilt again and agian. For now I did not have a full log.
I found there is same issue in this link. But we are using Solr 4.7.
http://lucene.472066.n3.nabble.com/how-to-avoid-recover-how-to-ensure-a-recover-success-td4096777.html