Indeed, I don't understand the caveat too, but I can imagine that is related
with some algorithm to trigger a full sync if necessary.
I will waiting for 5.3 to do the upgrade and have this configuration available.
—/Yago Riveiro
On Sun, Aug 23, 2015 at 3:37 AM, Shawn Heisey
Hi,
Can anyone explain me the possible causes of this warning?
too many updates received since start - startingUpdates no longer overlaps
with our currentUpdates
This warning triggers an full recovery for the shard that throw the warning.
-
Best regards
--
View this message in context
On 8/22/2015 11:51 AM, Yago Riveiro wrote:
My heap is about 24G an I tuned it using this link
https://wiki.apache.org/solr/ShawnHeisey#GC_Tuning_for_Solr
Shawn updated since I use it and some configuration are not in this document
any more.
I see on my GC logs pauses about 6s, my index
On 8/22/2015 3:50 PM, Yago Riveiro wrote:
I'm using java 7u25 oracle version with Solr 4.6.1
It work well with 98% of throughput but in some full GC the issue arises. A
full sync for one shard is more than 50G.
There is any configuration to configurate the number of docs behind leader
I'm using java 7u25 oracle version with Solr 4.6.1
It work well with 98% of throughput but in some full GC the issue arises. A
full sync for one shard is more than 50G.
There is any configuration to configurate the number of docs behind leader that
a replica can be?
On Sat, Aug 22,
,
Can anyone explain me the possible causes of this warning?
too many updates received since start - startingUpdates no longer overlaps
with our currentUpdates
This warning triggers an full recovery for the shard that throw the
warning.
-
Best regards
--
View this message in context
java 7u25, maybe upgrading to java 8 the GC pauses reduced.
I don't know if is safe use java 8 in production with solr ...
-
Best regards
--
View this message in context:
http://lucene.472066.n3.nabble.com/Too-many-updates-received-since-start-tp4224617p4224631.html
Sent from the Solr - User
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
the leader slice has received some documents (maybe about 1000 documents).
Solr fails to update peer sync with the log message:
Apr 21, 2012 10:13:40 AM org.apache.solr.update.PeerSync sync
WARNING: PeerSync: core=mycollection_slice21_shard1
url=zk-1:2181,zk-2:2181,zk-3:2181 too many updates
slice has received some documents (maybe about 1000 documents). Solr
fails to update peer sync with the log message:
Apr 21, 2012 10:13:40 AM org.apache.solr.update.PeerSync sync
WARNING: PeerSync: core=mycollection_slice21_shard1
url=zk-1:2181,zk-2:2181,zk-3:2181 too many updates received since
documents). Solr fails to update peer sync with the log message:
Apr 21, 2012 10:13:40 AM org.apache.solr.update.PeerSync sync
WARNING: PeerSync: core=mycollection_slice21_shard1
url=zk-1:2181,zk-2:2181,zk-3:2181 too many updates received since start
- startingUpdates no longer overlaps with our
11 matches
Mail list logo