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
I guess you can do this by switching off the source data center, but you would
need to look more in your architecture and especially applications that use
solr to verify this.
It may look easy but I would test it before.
> Am 06.06.2019 um 17:24 schrieb Joe Lerner :
>
> Ooohh...interesting. Th
Ooohh...interesting. Then, presumably there is some way to have what was the
cross-data-center replica become the new "primary"?
It's getting too easy!
Joe
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
An alternative to backup and restore could be the data center replication in
Solr:
https://lucene.apache.org/solr/guide/7_3/cross-data-center-replication-cdcr.html
> Am 05.06.2019 um 19:18 schrieb Joe Lerner :
>
> Hi,
>
> Our application is migrating from on-premise to AWS. We are currently on
On 6/5/2019 11:18 AM, Joe Lerner wrote:
Our application is migrating from on-premise to AWS. We are currently on
Solr Cloud 7.3.0.
We are interested in exploring ways to do this with minimal, down-time, as
in, maybe one hour.
One strategy would be to set up a new empty Solr Cloud instance in A
Hi,
Apache Solr is an open source project, with contributors and users doing our
best
to both document and answer questions, but sometimes it may take time, either
due
busy schedules or because the answer is unknown or an uncommon one that very few
have tried.
I suspect the last reason for the
Hi Ana,
There is no documentation because this is not something that is common.
Assuming you are using SolrCloud and that you don’t want any downtime. What you
could do is set up new Solr node on the same box but configure it to use this
new disk. After it is set, you use ADDREPLICA and REMOVERE
Hello guys,
I would appreciate if you could kindly treat this topic with priority as
the lack of documentation is kind of a blocker for us.
Thanks in advance,
Ana
On Mon, Jun 18, 2018 at 4:56 PM, Ana Mercan (RO) wrote:
> Hi,
>
> I have the following scenario, I'm having a shared cluster solr
On 10/15/2015 9:53 AM, fabigol wrote:
> i catch an old project working with Solr 1.4.1, jbossPortal and java 1.5.
> I try to migrate my solr version to solr 5.2.1 work with java 1.7.
> The solr indexation works but i fail to display the new results on my
> application.
> I want to know if i must
Solr does not guarantee backwards compatibility more than one major
version back. That is,
Solr 3.x is guaranteed to at least read Solr 1.4 indexes (there was no
Solr 2.x).
Solr 4x can read 3x but not 1.x.
Solr 5x can read 4x indexes, but not 3x
You really only have two choices here. You _could_
21 matches
Mail list logo
