Hi Erick/Shawn,
I went for the deleteById option but still under heavy load on my test machine
I still see issues with the nodes going into recovery. I've also noticed in my
testing that the leader changed and one node was down for a period before going
into recovery. The two errors I see in th
lucene.apache.org
Subject: Re: CloudSolrClient (any version). Find the node your query has
connected to.
WARNING - External email from lucene.apache.org
You have to be a little careful here, one thing I learned relatively recently
is that there are in-memory structures that hold pointers to _all_
Sent: 22 May 2019 20:17
To: solr-user@lucene.apache.org
Subject: Re: CloudSolrClient (any version). Find the node your query has
connected to.
WARNING - External email from lucene.apache.org
You have to be a little careful here, one thing I learned relatively recently
is that there are in-m
Try to add &shards.info=true to your request. It will return a section telling
exactly what shards/replicas served that request with counts and all :)
Jan Høydahl
> 22. mai 2019 kl. 21:17 skrev Erick Erickson :
>
> You have to be a little careful here, one thing I learned relatively recently
>
You have to be a little careful here, one thing I learned relatively recently
is that there are in-memory structures that hold pointers to _all_
un-searchable docs (i.e. no new searchers have been opened since the doc was
added/updated) to support real-time get. So if you’re indexing a _lot_ of
On 5/22/2019 10:47 AM, Russell Taylor wrote:
I will add that we have set commits to be only called by the loading program.
We have turned off soft and autoCommits in the solrconfig.xml.
Don't turn off autoCommit. Regular hard commits, typically with
openSearcher set to false so they don't in
Erick Erickson [mailto:erickerick...@gmail.com]
> Sent: 22 May 2019 15:50
> To: solr-user@lucene.apache.org
> Subject: Re: CloudSolrClient (any version). Find the node your query has
> connected to.
>
> WARNING - External email from lucene.apache.org
>
> Why do you want to know? You’
ecovery mode.
>
> I hope that explains the problem, thanks for your time.
>
> Regards
>
> Russell Taylor
>
>
>
> -Original Message-
> From: Erick Erickson [mailto:erickerick...@gmail.com]
> Sent: 22 May 2019 15:50
> To: solr-user@lucene.apache.o
thanks for your time.
Regards
Russell Taylor
-Original Message-
From: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: 22 May 2019 15:50
To: solr-user@lucene.apache.org
Subject: Re: CloudSolrClient (any version). Find the node your query has
connected to.
WARNING - External
Why do you want to know? You’ve asked how do to X without telling us what
problem Y you’re trying to solve (the XY problem) and frequently that leads to
a lot of wasted time…..
Under the covers CloudSolrClient uses a pretty simple round-robin load balancer
to pick a Solr node to send the query
You have to provide the addresses of the zookeeper ensemble - it will figure it
out on its own based on information in Zookeeper.
> Am 22.05.2019 um 14:38 schrieb Russell Taylor :
>
> Hi,
> Using CloudSolrClient, how do I find the node (I have 3 nodes for this
> collection on our 6 node cluster
Hi,
Using CloudSolrClient, how do I find the node (I have 3 nodes for this
collection on our 6 node cluster) the query has connected to.
I'm hoping to get the full URL if possible.
Regards
Russell Taylor
This message may contain confidential information and
12 matches
Mail list logo
