Hi all,
I use SOLR-6.5.1. Before couple weeks I started to use replication feature
in cloud mode without override default behavior of ReplicationHandler.
After deployment replication feature to production, almost every day I hit
these errors:
SolrException: Unable to download completely.
Shawn,
Thanks for the info. We’ve been running this way for the past 4 years.
We were running on very large hardware, 20 physical cores with 256 gigs of ram
with 3 billion document and it was the only way we could take advantage of the
hardware.
Running 1 Solr instance per server never gave
On 9/25/2018 9:21 AM, Chuck Reynolds wrote:
Each server has three instances of Solr running on it so every instance on the
server has to be in the same replica set.
You should be running exactly one Solr instance per server. When
evaluating rules for replica placement, SolrCloud will treat
What specifically do you control? Just keyword (and "Communities:"
part is locked?) or anything after q= or anything that allows multiple
variables?
Because if you could isolate search value, you could use for example
facet.prefix, set in solrconfig as a default parameter and populated
from the
you can update your filter query to be a facet query, this will apply the
query to the resulting facet set instead of the Communities field itself.
--
John Blythe
On Tue, Sep 25, 2018 at 4:15 PM Hanjan, Harinder
wrote:
> Hello!
>
> I am doing faceting on a field which has multiple values and
Hello!
I am doing faceting on a field which has multiple values and it's yielding
expected but undesireable results. I need different behaviour but not sure how
to formulate a query for it. Here is my current setup.
= Data Set =
{
"Communities":["BANFF TRAIL - BNF", "PARKDALE -
Steve,
Sorry must have omitted it from a past response.
Here is what came back from the response.
40091org.apache.solr.common.SolrException:org.apache.solr.common.SolrException:
Could not identify nodes matching the rules [{
"shard":"*",
"replica":"1",
"sysprop.AWSAZ":"AZ1"}, {
Chuck, see my responses inline below:
> On Sep 25, 2018, at 12:50 PM, Chuck Reynolds wrote:
> The bottom line is I guess I'm confused by the documentation and the
> reference to replicas. Normally when referring to replicas in the
> documentation it is referring to the number of times you want
What does "Failed solr node" mean? How do you mean if fails? There's
lots of recovery built in for a replica that gets out-of-sync somehow
(is shut down while indexing is going on etc). All that relies on
having more than one replica per shard of course.
If the node completely dies due to
Steve,
No doubt I confused you. I'm confused myself__
When I said replica set what I was referring to was one of the three replicas
of the data. Each replica needing to be in a different AZ.
What is a "replica set”? And why does each instance of Solr (referred to in
the reference guide as
Hi Chuck, see my replies inline below:
> On Sep 25, 2018, at 11:21 AM, Chuck Reynolds wrote:
>
> So we have 90 server in AWS, 30 servers per AZ's.
> 90 shards for the cluster.
> Each server has three instances of Solr running on it so every instance on
> the server has to be in the same
Hi,
Is there a recommend design pattern or best practice for auto recovery of a
failed Solr Node?
I'm I correct to assume there is nothing out of the box for this and we have to
code our own solution?
Thanks
Michael Kimber
This electronic message may contain proprietary and confidential
Steve,
Yes I set the set system property AWSAZ and I've checked the java properties in
Solr and I can see them.
It maybe the way we are configuring Solr so let me explain that first.
So we have 90 server in AWS, 30 servers per AZ's.
90 shards for the cluster.
Each server has three instances of
Chuck,
The default Snitch is the one that’s used if you don’t specify one in a rule.
The sysprop.* tag is provided by the default Snitch.
The only thing that seems wrong to me in your rules is “replica:1”,
“replica:2”, and “replica:3” - these say that exactly one, two, and three
replicas of
Hi all,
The Javadocs for ConcurrentUpdateSolrClient steer users away from
using it for query requests:
"Although any SolrClient request can be made with this implementation,
it is only recommended to use ConcurrentUpdateSolrClient with /update
requests. The class HttpSolrClient is better suited
Steve,
I wasn't able to get the sysprop to work. I think maybe there is a disconnect
on my part.
From the documentation it looks like I can only use the sysprop tag if I'm
using a Snitch. Is that correct.
I can't find any example of anyone using the default Snitch.
Here is what I have for
Hi,
I am working on a test setup with Solr 6.1.0 cloud with 1 collection
sharded across 2 shards with no replication. When triggered a SPLITSHARD
command it throws "java.lang.OutOfMemoryError: Java heap space" everytime.
I tried this with multiple heap settings of 8, 12 & 20G but every time it
Hi,
I am trying to get Index stats using luke request and CloudSolrClient but it is
not returning index stats from all the shards of a collection.
Each request returns a different result from a different shard.
Is there way I can get Index statistics of collection is SOLR cloud?
For a
Hi,
Solr does not do anything automatically, so I think this is a question for the
Nutch community - http://nutch.apache.org/mailing_lists.html
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
> 24. sep. 2018 kl. 20:06 skrev Bineesh :
>
> Team,
>
> We use solr 7.3.1
Team,
We use solr 7.3.1 and Nucth 1.15.
I created two collections in solr and data successfully indexed from Nutch
after crawling. Up on the third collection index in solr, i see that first
collecion indexed data automatically clears.Pls suggest
--
Sent from:
20 matches
Mail list logo
