Hi all,
Please could someone review #4395<https://github.com/apache/geode/pull/4395>.
BR,
Mario
Šalje: Mario Kevo
Poslano: 17. prosinca 2019. 14:30
Prima: Jason Huynh
Kopija: geode
Predmet: Odg: Odg: Odg: Odg: Odg: Lucene upgrade
Hi Jason,
Nice ca
: Odg: Odg: Odg: Lucene upgrade
Hi Mario,
I think I see what is going on here. The logic for "reindex" code was a bit
off ( it expected reindex features to be complete by a certain release). I
have a PR on develop to adjust that calculation
(https://github.com/apache/geode/pull/
In tests it tried to execute a query after all members are rolled.
>
> BR,
> Mario
>
> --
> *Šalje:* Jason Huynh
> *Poslano:* 11. prosinca 2019. 23:08
> *Prima:* Mario Kevo
> *Kopija:* geode
> *Predmet:* Re: Odg: Odg: Odg: Lucene upgrade
query after all members are rolled.
BR,
Mario
Šalje: Jason Huynh
Poslano: 11. prosinca 2019. 23:08
Prima: Mario Kevo
Kopija: geode
Predmet: Re: Odg: Odg: Odg: Lucene upgrade
Hi Mario,
Is the same test failing? If it's a different test, could you tell us
Huynh
> *Poslano:* 6. prosinca 2019. 20:53
> *Prima:* Mario Kevo
> *Kopija:* geode
> *Predmet:* Re: Odg: Odg: Lucene upgrade
>
> Hi Mario,
>
> I made a PR against your branch for some of the changes I had to do to get
> past the Index too new exception. Summary - r
lower number of
entries in tests?
BR,
Mario
Šalje: Jason Huynh
Poslano: 6. prosinca 2019. 20:53
Prima: Mario Kevo
Kopija: geode
Predmet: Re: Odg: Odg: Lucene upgrade
Hi Mario,
I made a PR against your branch for some of the changes I had to do to get past
2> tid=0x46] During normal
> processing, unsuccessfully dispatched 1 events (batch #0)*
> For VM0(server1) and VM2(server3) it has 14 entries, one is unsuccessfully
> dispatched.
>
> I don't know why some events are successfully dispatched, some not.
> Do you have any idea?
is unsuccessfully
dispatched.
I don't know why some events are successfully dispatched, some not.
Do you have any idea?
BR,
Mario
Šalje: Jason Huynh
Poslano: 2. prosinca 2019. 18:32
Prima: geode
Predmet: Re: Odg: Lucene upgrade
Hi Mario,
Sorry I reread the origin
Hi Mario,
Sorry I reread the original email and see that the exception points to a
different problem.. I think your fix addresses an old version seeing an
unknown new lucene format, which looks good. The following exception looks
like it's the new lucene library not being able to read the older f
I started with implementation of Option-1.
As I understood the idea is to block all puts(put them in the queue) until all
members are upgraded. After that it will process all queued events.
I tried with Dan's proposal to check on start of LuceneEventListener.process()
if all members are upgrade
10 matches
Mail list logo
