Haddorp [mailto:hendrik.hadd...@gmx.net]
Sent: Friday, January 25, 2019 11:39 AM
To: solr-user@lucene.apache.org
Subject: SolrCloud recovery
Hi,
I have a SolrCloud with many collections. When I restart an instance and
the replicas are recovering I noticed that number replicas recovering at
one poin
t; parallel.
> >
> > https://lucene.apache.org/solr/guide/7_6/format-of-solr-xml.html
> >
> >>> -Original Message-
> >>> From: Hendrik Haddorp [mailto:hendrik.hadd...@gmx.net]
> >>> Sent: Friday, January 25, 2019 11:39 AM
> >>> T
.html
-Original Message-
From: Hendrik Haddorp [mailto:hendrik.hadd...@gmx.net]
Sent: Friday, January 25, 2019 11:39 AM
To: solr-user@lucene.apache.org
Subject: SolrCloud recovery
Hi,
I have a SolrCloud with many collections. When I restart an instance and
the replicas are recovering I no
x.net]
> > Sent: Friday, January 25, 2019 11:39 AM
> > To: solr-user@lucene.apache.org
> > Subject: SolrCloud recovery
> >
> > Hi,
> >
> > I have a SolrCloud with many collections. When I restart an instance and
> > the replicas are recovering I noti
You can try to tweak solr.xml
> -Original Message-
> From: Hendrik Haddorp [mailto:hendrik.hadd...@gmx.net]
> Sent: Friday, January 25, 2019 11:39 AM
> To: solr-user@lucene.apache.org
> Subject: SolrCloud recovery
>
> Hi,
>
> I have a SolrCloud with many col
Hi,
I have a SolrCloud with many collections. When I restart an instance and
the replicas are recovering I noticed that number replicas recovering at
one point is usually around 5. This results in the recovery to take
rather long. Is there a configuration option that controls how many
replica
ou should get the
> count
> of docs in it.
>
> Most likely, since the replica is recovering it is forwarding all queries
> to
> the active replica, this can be verified in the core logs.
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.c
.nabble.com/Question-about-solrcloud-recovery-process-tp4145450p4145491.html
Sent from the Solr - User mailing list archive at Nabble.com.
No, we're not doing NRT. The search clients aren't using CloudSolrServer
and they are behind an AWS load balancer, which calls the Solr ping handler
(implemented with ClusterStateAwarePingRequestHandler) to determine when
the node is active. This ping handler also responds during the index copy,
wh
I don’t know offhand about the num docs issue - are you doing NRT?
As far as being able to query the replica, I’m not sure anyone ever got to
making that fail if you directly query a node that is not active. It certainly
came up, but I have no memory of anyone tackling it. Of course in many othe
I bring up a new Solr node with no index and watch the index being
replicated from the leader. The index size is 12G and the replication takes
about 6 minutes, according to the replica log (from 'Starting recovery
process' to 'Finished recovery process). However, shortly after the
replication begin
The version is 4.6. I am going to ask for the log files and post it.
-Original Message-
From: Mark Miller [mailto:markrmil...@gmail.com]
Sent: Thursday, March 06, 2014 6:33 PM
To: solr-user
Subject: Re: SolrCloud recovery after nodes are rebooted in rapid succession
Would probably need
Would probably need to see some logs to say much. Need to understand why they
are inoperable.
What version is this?
- Mark
http://about.me/markrmiller
On Mar 6, 2014, at 6:15 PM, Nazik Huq wrote:
> Hello,
>
>
>
> I have a question from a colleague who's managing a 3-node(VMs) SolrCloud
>
Hello,
I have a question from a colleague who's managing a 3-node(VMs) SolrCloud
cluster with a separate 3-node Zookeeper ensemble. Periodically the data
center underneath the SolrCloud decides to upgrade the SolrCloud instance
infrastructure in a "rolling upgrade" fashion. So after the 1st i
14 matches
Mail list logo
