eode.apache.org
Subject: Re: [DISCUSS] Upgrading to Lucene 7.1.0
But Mario, just for my clarification, if we re-enable the queries in the tests
in the mixed version servers mode, it goes into a stackoverflow situation. That
what i saw when i set hasLuceneVersionMismatch(host) to false in the t
n executions
> get repeatedly executed and that results in stack overflow.
>
>
>
> From: Nabarun Nag
> Sent: Monday, September 27, 2021 2:30 PM
> To: dev@geode.apache.org
> Subject: Re: [DISCUSS] Upgrading to Lucene 7.1.0
>
> In sim
JXVCI6Mn0%3D%7C1000&sdata=E%2FIR9IdWMBWOrZl%2FYYnRHOOuLccmbvet6fyOgx%2FFeBk%3D&reserved=0>
BR,
Mario
Šalje: Udo Kohlmeyer
Poslano: 28. rujna 2021. 1:44
Prima: dev@geode.apache.org
Predmet: Re: [DISCUSS] Upgrading to Lucene 7.1.0
Might I propose s
and safely
initialize it.
I think this approach allows for a more seamless (lower downtime) upgrading of
system and extension components.
Thoughts?
--Udo
From: Nabarun Nag
Date: Tuesday, September 28, 2021 at 7:33 AM
To: dev@geode.apache.org
Subject: Re: [DISCUSS] Upgrading to Lucene 7.1.0
:30 PM
To: dev@geode.apache.org
Subject: Re: [DISCUSS] Upgrading to Lucene 7.1.0
In simple words, if Lucene indexes were created by a new version (7.1.0), then
replicated to others that are still in the older version, they won't understand
the index, and the event processors start thr
yManager.java:42)
[vm2_v1.2.0] at
org.apache.geode.cache.lucene.internal.AbstractPartitionedRepositoryManager.lambda$computeRepository$0(AbstractPartitionedRepositoryManager.java:116)
[vm2_v1.2.0] ... 10 more
From: Jacob Barrett
Sent: Monday, September 27, 2021 2:08 PM
To: dev@geode.apache.org
Subject:
> On Sep 27, 2021, at 11:48 AM, nabarun nag wrote:
>
> Recently, a commit was pushed to develop which upgraded the Lucene
> version used in Apache Geode to 7.1.0. These new Lucene indexes are
> not compatible with the previous versions hence it breaks the rolling
> upgrade contract. We are no
Does anyone have more context on why lucene queries won't work during the
rolling upgrade? I can see what added a line to the documentation and changed
the tests not to do queries, but I'm not sure why we needed to do that.
-Dan
From: nabarun nag
Sent: Monday,
Would it be possible to allow an operator to choose which version of Lucene to
use? Such that if they are prepared for the issues you describe, they could
still go ahead and upgrade to 7.10. Or are there breaking API changes which
would make that hard/impossible to accommodate in our code base?
