Hi, everyone,
The data is not synchronized to the pull replica from tlog solr node.
We are using a replica of tlog and pull.
We are trying to change the version of solr we use from 7.5.0 to 8.6.2.
Configuration :
The pull node is being started after the tlog node is filled with data.
Problem.
Hi all,
Maybe a tricky question little bit, but I need to ask. Let's say I have
infinite RAM and infinite SSDs, but I have deficiency of CPU (Lets's say 4
CPU for each shard). So, my question is which is more preferable:
1. One leader with 4 CPU
OR
2. One leader with 2 CPU and one replica with
seconds, shouldn't ZK promote replica
to leader? I am not sure how increasing zk timeout will help.
-Original Message-
From: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: Wednesday, January 28, 2015 11:42 AM
To: solr-user@lucene.apache.org
Subject: Re: replica never takes
We're using Solr 4.8.0
-Original Message-
From: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: Tuesday, January 27, 2015 7:47 PM
To: solr-user@lucene.apache.org
Subject: Re: replica never takes leader role
What version of Solr? This is an ongoing area of improvements and several
-Original Message-
From: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: Tuesday, January 27, 2015 7:47 PM
To: solr-user@lucene.apache.org
Subject: Re: replica never takes leader role
What version of Solr? This is an ongoing area of improvements and several
are very recent
down and it
doesn't talk to zookeeper for 45 seconds, shouldn't ZK promote replica to
leader? I am not sure how increasing zk timeout will help.
-Original Message-
From: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: Wednesday, January 28, 2015 11:42 AM
To: solr-user
Hello,
We have SolrCloud cluster (5 shards and 2 replicas) on 10 boxes and three
zookeeper instances. We have noticed that when a leader node goes down the
replica never takes over as a leader, cloud becomes unusable and we have to
bounce entire cloud for replica to assume leader role
boxes and three
zookeeper instances. We have noticed that when a leader node goes down the
replica never takes over as a leader, cloud becomes unusable and we have to
bounce entire cloud for replica to assume leader role. Is this default
behavior? How can we change this?
Thanks.
without losing docs in this scenario?
Thanks.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Replica-as-a-leader-tp4135614p4136729.html
Sent from the Solr - User mailing list archive at Nabble.com.
--
Anshum Gupta
http://www.anshumgupta.net
the replica with the docs that were indexed to the
leader.
Is there a way that solr can recover without losing docs in this scenario?
Thanks.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Replica-as-a-leader-tp4135614p4136729.html
Sent from the Solr - User mailing list archive
.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Replica-as-a-leader-tp4135614p4136729.html
Sent from the Solr - User mailing list archive at Nabble.com.
--
Anshum Gupta
http://www.anshumgupta.net
(*active status, not leader!!!*).
Expected:
5. To stay in down status.
*6. Not to handel index, commit and search requests - no servers hosting
shards!*
Thanks!
--
View this message in context:
http://lucene.472066.n3.nabble.com/Replica-as-a-leader-tp4135077.html
Sent from the Solr - User
was recovering for 2-3
minutes and then it became active (not leader in cluster state).
Index, commit and search requests are handled in the other replica
(active status, not leader!!!).
The search Results not includes docs that have been indexed to the leader
in step 3. *
6. syncing
.n3.nabble.com/Replica-as-a-leader-tp4135077.html
Sent from the Solr - User mailing list archive at Nabble.com.
14 matches
Mail list logo
