Thanks Erick.
I am going through the recommendations given in this email chain.
Best,
Modassar
On Thu, Nov 5, 2020 at 7:17 PM Erick Erickson
wrote:
> Oh dear.
>
> You made me look at the reference guide. Ouch.
>
> We have this nice page “Defining core.properties” that talks about
> defining co
Oh dear.
You made me look at the reference guide. Ouch.
We have this nice page “Defining core.properties” that talks about defining
core.properties. Unfortunately it has _no_ warning about the fact that trying
to use this in SolrCloud is a really bad idea. As in “don’t do it”. To make
matters
Hi Shawn,
I understand that we do not need to modify the core.properties and use the
APIs to create core and collection and that is what I am doing now.
This question of naming the core as per the choice comes from our older
setup where we have 12 shards, a collection and core both named the same
On 11/4/2020 9:32 PM, Modassar Ather wrote:
Another thing: how can I control the core naming? I want the core name to
be *mycore* instead of *mycore**_shard1_replica_n1*/*mycore*
*_shard2_replica_n2*.
I tried setting it using property.name=*mycore* but it did not work.
What can I do to achieve th
Hi Erick,
I have put solr configs in Zookeeper. I have created a collection using the
following API.
admin/collections?action=CREATE&name=mycore&numShards=2&replicationFactor=1&collection.configName=mycore&
property.name=mycore
The collection got created and I can see *mycore**_shard1_replica_n1*
inline
> On Nov 4, 2020, at 2:17 AM, Modassar Ather wrote:
>
> Thanks Erick and Ilan.
>
> I am using APIs to create core and collection and have removed all the
> entries from core.properties. Currently I am facing init failure and
> debugging it.
> Will write back if I am facing any issues.
>
Thanks Erick and Ilan.
I am using APIs to create core and collection and have removed all the
entries from core.properties. Currently I am facing init failure and
debugging it.
Will write back if I am facing any issues.
Best,
Modassar
On Wed, Nov 4, 2020 at 3:20 AM Erick Erickson
wrote:
> Do n
Do note, though, that the default value for legacyCloud changed from
true to false so even though you can get it to work by setting
this cluster prop I wouldn’t…
The change in the default value is why it’s failing for you.
> On Nov 3, 2020, at 11:20 AM, Ilan Ginzburg wrote:
>
> I second Erick'
I second Erick's recommendation, but just for the record legacyCloud was
removed in (upcoming) Solr 9 and is still available in Solr 8.x. Most
likely this explains Modassar why you found it in the documentation.
Ilan
On Tue, Nov 3, 2020 at 5:11 PM Erick Erickson
wrote:
> You absolutely need co
You absolutely need core.properties files. It’s just that they
should be considered an “implementation detail” that you
should rarely, if ever need to be aware of.
Scripting manual creation of core.properties files in order
to define your collections has never been officially supported, it
just ha
Thanks Erick for your response.
I will certainly use the APIs and not rely on the core.properties. I was
going through the documentation on core.properties and found it to be still
there.
I have all the solr install scripts based on older Solr versions and wanted
to re-use the same as the core.pro
You’re relying on legacyMode, which is no longer supported. In
older versions of Solr, if a core.properties file was found on disk Solr
attempted to create the replica (and collection) on the fly. This is no
longer true.
Why are you doing it this manually instead of using the collections API?
You
12 matches
Mail list logo
