Hey guys I’m try to do a backup of my Solr cloud cluster but it is never
starting.
When I execute the async backup command it returns quickly like I would expect
with the following response
0111234
But the backup never starts.
When I execute the REQUESTSTATUS it response with the followin
We are running Solr 6.6
Sent from my iPhone
> On May 25, 2019, at 12:45 PM, Mikhail Khludnev wrote:
>
> Hello, Chuck.
>
> Which version do you run?
> Can't you encounter
> https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_bro
I have 4 instances of Solr running on 3 servers with a replication factor of 3.
They are using ports 10001 -10004
Server 1 10.xxx.xxx.75
Server 2 10.xxx.xxx.220
Server 3 10.xxx.xxx.245
When I execute the command to do the restore to a new cluster it create each
master with the same IP address
I have 4 instances of Solr running on 3 servers with a replication factor of 3.
When I execute the command to do the restore to a new TEST cluster it create
each master with the same IP address and port but all subsequent replicas are
create correctly. That means that the other 3 instances of s
=BTS
Then start Solr and it would create the sharding base on the information in the
core.properties file.
When I try it with Solr 6.6 it seem to ignore the core.properties file.
Thanks again for your help
On 10/1/18, 11:21 PM, "Varun Thacker" wrote:
Hi Chuck,
I was cha
Solr
which has the policy based replica placement. Unfortunately, I don't
have any other solution I can think of
On Wed, Sep 26, 2018 at 11:46 PM Chuck Reynolds
wrote:
>
> Noble,
>
> So other than manually moving replicas of shard do you hav
we should be investing our resources here
On Wed, Sep 26, 2018 at 1:23 PM Chuck Reynolds
wrote:
>
> 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 wit
us the throughput we needed.
So I somewhat disagree with your statement because our test proved otherwise.
Thanks for the info.
Sent from my iPhone
> On Sep 25, 2018, at 4:19 PM, Shawn Heisey wrote:
>
>> On 9/25/2018 9:21 AM, Chuck Reynolds wrote:
>> Each server has three
2"},
"10.157.116.201:10001_solr":{"sysprop.AWSAZ":"AZ2"},
"10.157.115.30:10002_solr":{"sysprop.AWSAZ":"AZ1"}}400org.apache.solr.common.SolrExceptionorg.apache.solr.common.SolrExceptionCould not identify nodes matching the rules
tion factor of three
correctly shards the data across three AZ so if I was to lose one or even two
AZ's in AWS Solr would still have 1 - 2 copies of the data. How would that
rule work?
On 9/25/18, 10:17 AM, "Steve Rowe" wrote:
Hi Chuck, see my replies inline below:
a. Does that
make sense?
On 9/25/18, 9:08 AM, "Steve Rowe" wrote:
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 “
what I have for my rule:
rule=shard:*,replica:1,sysprop.AWSAZ:AZ1&rule=shard:*,replica:2,sysprop.AWSAZ:AZ2&rule=shard:*,replica:3,sysprop.AWSAZ:AZ3
I'm not specifying a snitch. Is that my problem or is there a problem with my
rule?
Thanks for your help.
On 9/21/18, 2:40 PM, "
8, 2:40 PM, "Steve Rowe" wrote:
Hi Chuck,
One way to do it is to set a system property on the JVM running each Solr
node, corresponding to the the AWS availability zone on which the node is
hosted.
For example, you could use sysprop “AWSAZ”, then use rules like:
I'm using Solr 6.6 and I want to create a 90 node cluster with a replication
factor of three. I'm using AWS EC2 instances and I have a requirement to
replicate the data into 3 AWS availability zones.
So 30 servers in each zone and I don't see a create collection rule that
will put one replica i
I have a use case where I need to create a Solr 6.6 cluster in AWS. The
collection will have a replication factor of 3 and needs to be in 3 different
Availability Zones.
I’ve read the documentation on Rule-based Replica Placement but it doesn’t seem
to be very clear how I would tag servers so
Hello Jonas,
Did you figure this out?
Dr. Chuck Brooks
248-838-5070
-Original Message-
From: Jonas Vasiliauskas [mailto:jonas.vasiliaus...@yahoo.com.INVALID]
Sent: Saturday, July 02, 2016 11:37 AM
To: solr-user@lucene.apache.org
Subject: Data import handler in techproducts example
There's a mistake in the sample xml at
https://wiki.apache.org/solr/AnalyzersTokenizersTokenFilters#solr.PatternCaptureGroupFilterFactory
In the XML snippet instead of
class="solr.PatternCaptureGroupTokenFilter"
you should have
class="solr.PatternCaptureGroupFilterFactory"
(ie, the title
Hello all,
is there support for non-english language content indexing in Solr?
I'm interested in Bulgarian, Hungarian, Romanian and Russian.
Best regards,
Chuck
req.setParam("overwrite", "true");
req.setParam("commit", "true");
- in the query:
http://localhost:8983/solr/select?q=attr_content:%22Django%22&rows=4
- edit the solrconfig.xml in the requesthandler params
id,title
so that you won't get the
0.5
[-\w ,/\n\"']{20,200}
true
The schema.xml is untouched and downloaded yesterday from the latest stable
build.
At first, I thought it had something to do with the extraction of the pdf,
but I tried the demo xml docs also and got the same result.
I'm new to this, so please help.
Thank you,
Chuck
20 matches
Mail list logo
