redmet: Re: [DISCUSS] Upgrading to Lucene 7.1.0
My understanding from our previous discussion about upgrading lucene was that
we talked about pausing the asynchronous indexing process during the rolling
upgrade. I don't remember a discussion that it was ok to not allow queries
during the upgra
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
From: Mario Kevo
Sent: Tuesday, September 28, 2021 4:49 AM
To: dev@geode.apache.org
Subject: Odg: [DISCUSS] Upgrading to Lucene 7.1.0
Hi all,
Just a small clarification of the reverted PR.
There were a lot of changes between Lucene versions 6.x and 7.x. There is an
article for
ward%20Lucene%20upgrade+page:4+mid:ygjhsuikdrbuihap+state:results>
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 something here.
There is currently a si
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
nt: Monday, September 27, 2021 11:48 AM
To: dev@geode.apache.org
Subject: [DISCUSS] Upgrading to Lucene 7.1.0
Hi dev team,
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 version
?
--Jens
From: nabarun nag
Date: Monday, September 27, 2021 at 11:49 AM
To: dev@geode.apache.org
Subject: [DISCUSS] Upgrading to Lucene 7.1.0
Hi dev team,
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
Hi dev team,
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 longer able to execute Lucene queries when
there are
12 matches
Mail list logo
