-
From: Oakley, Craig (NIH/NLM/NCBI) [C]
Sent: Friday, August 10, 2018 12:54 PM
To: solr-user@lucene.apache.org
Subject: RE: sharding and placement of replicas
Note that I usually create collections with commands which contain (for example)
solr/admin/collections?action=CREATE&name=collec
g (NIH/NLM/NCBI) [C] [mailto:craig.oak...@nih.gov]
Sent: Thursday, August 09, 2018 5:08 PM
To: solr-user@lucene.apache.org
Subject: RE: sharding and placement of replicas
Okay, I've tried again with two nodes running Solr7.4 on different hosts.
Before SPLITSHARD, collectest2_shard1_replica_n1 was on
ckson [mailto:erickerick...@gmail.com]
Sent: Tuesday, July 31, 2018 5:16 PM
To: solr-user
Subject: Re: sharding and placement of replicas
Right, two JVMs on the same physical host with different ports are
"different Solrs" by default. If you had two replicas per shard and
both were
:apa...@elyograg.org]
> Sent: Tuesday, July 31, 2018 2:26 PM
> To: solr-user@lucene.apache.org
> Subject: Re: sharding and placement of replicas
>
> On 7/27/2018 8:26 PM, Erick Erickson wrote:
>> Yes with some fiddling as far as "placement rules", start here:
>> ht
, July 31, 2018 2:26 PM
To: solr-user@lucene.apache.org
Subject: Re: sharding and placement of replicas
On 7/27/2018 8:26 PM, Erick Erickson wrote:
> Yes with some fiddling as far as "placement rules", start here:
> https://lucene.apache.org/solr/guide/6_6/rule-based-replica-placem
On 7/27/2018 8:26 PM, Erick Erickson wrote:
> Yes with some fiddling as far as "placement rules", start here:
> https://lucene.apache.org/solr/guide/6_6/rule-based-replica-placement.html
>
> The idea (IIUC) is that you provide a snitch" that identifies what
> "rack" the Solr instance is on and can
bq. Could SolrCloud avoid putting multiple replicas of the same shard
on the same host when there are multiple nodes per host?
Yes with some fiddling as far as "placement rules", start here:
https://lucene.apache.org/solr/guide/6_6/rule-based-replica-placement.html
The idea (IIUC) is that you pro
On 7/25/2018 3:49 PM, Oakley, Craig (NIH/NLM/NCBI) [C] wrote:
> I end up with four cores instead of two, as expected. The problem is that
> three of the four cores (col_shard1_0_replica_n5, col_shard1_0_replica0 and
> col_shard1_1_replica_n6) are *all on hostname1*. Only col_shard1_1_replica0
>
Original Message-
From: Shawn Heisey [mailto:apa...@elyograg.org]
Sent: Tuesday, June 19, 2018 2:20 PM
To: solr-user@lucene.apache.org
Subject: Re: sharding and placement of replicas
On 6/15/2018 11:08 AM, Oakley, Craig (NIH/NLM/NCBI) [C] wrote:
> If I start with a collection X on two nodes
On 6/15/2018 11:08 AM, Oakley, Craig (NIH/NLM/NCBI) [C] wrote:
> If I start with a collection X on two nodes with one shard and two replicas
> (for redundancy, in case a node goes down): a node on host1 has
> X_shard1_replica1 and a node on host2 has X_shard1_replica2: when I try
> SPLITSHARD, I
10 matches
Mail list logo