On 12/27/2017 3:02 AM, Gopesh Sharma wrote:
> We had two system where we were doing Master Slave Replication, we used to do
> delta-import every 24 hours since we did not want the near real-time data.
> Now since our data is increasing we thought of adding one more machine to the
> master slave
Hello All,
We had two system where we were doing Master Slave Replication, we used to do
delta-import every 24 hours since we did not want the near real-time data. Now
since our data is increasing we thought of adding one more machine to the
master slave replication.
I thought of creating a Sh
ific cases and environments.
Alex
-Original Message-
From: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: Sunday, June 23, 2013 20:41
To: solr-user@lucene.apache.org
Subject: Re: Sharding and Replication
Asif:
Thanks, this is great info and may add to the priority of m
you'll won't get any
>> >> batching. If you send 10 docs at a time and they happen to
>> >> go to 10 different shards, you'll get 10 different update
>> >> requests.
>> >>
>> >> If you're sending 1,000 docs per update y
give a option to batch N
> >> updates in either of the above case
> >>
> >> I suspect what you're seeing is that you're not sending very
> >> many docs per update request and so are being mislead.
> >>
> >> But that's a guess since
x27;re seeing is that you're not sending very
>> many docs per update request and so are being mislead.
>>
>> But that's a guess since you haven't provided much in the
>> way of data on _how_ you're updating.
>>
>> bq: the cloud eventually starts
pdating.
>
> bq: the cloud eventually starts to fail
> How? Details matter.
>
> Best
> Erick
>
> On Wed, Jun 19, 2013 at 4:23 AM, Asif wrote:
> > Hi,
> >
> > I had questions on implementation of Sharding and Replication features of
> > Solr/Cloud.
>
hat's a guess since you haven't provided much in the
way of data on _how_ you're updating.
bq: the cloud eventually starts to fail
How? Details matter.
Best
Erick
On Wed, Jun 19, 2013 at 4:23 AM, Asif wrote:
> Hi,
>
> I had questions on implementation of Sharding and Repl
On Wed, Jun 19, 2013 at 11:12 PM, Asif wrote:
> Hi,
>
> I had questions on implementation of Sharding and Replication features of
> Solr/Cloud.
>
> 1. I noticed that when sharding is enabled for a collection - individual
> requests are sent to each node serving as a shard.
Hi,
I had questions on implementation of Sharding and Replication features of
Solr/Cloud.
1. I noticed that when sharding is enabled for a collection - individual
requests are sent to each node serving as a shard.
2. Replication too follows above strategy of sending individual documents
to the
Hi,
I had questions on implementation of Sharding and Replication features of
Solr/Cloud.
1. I noticed that when sharding is enabled for a collection - individual
requests are sent to each node serving as a shard.
2. Replication too follows above strategy of sending individual documents
to the
ion_HA.png
Solr_Sharding_and_Replication_HA.png
Basically, it's a combination of sharding and replication.
Server 1, I have a 3-core Solr instance. e.g.: Master 1, Slave 1 (replicated
locally from Master 1) and Slave 2 (replicated remotely from Master 2 in
Server 2)
Server 2, I have similar setup, e.g.: Master 2, Slav
12 matches
Mail list logo
