Re: [DISCUSS] Upgrading to Lucene 7.1.0

2021-09-28 Thread Dan Smith
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 upgrade. But this is what we added to the docs: "All c

Re: [DISCUSS] Upgrading to Lucene 7.1.0

2021-09-28 Thread Jacob Barrett
I asked this previously but didn’t see a response in the follow ups. If were were to improve upon the code so that it didn’t stack overflow when it can’t read the index version on a specific member/bucket, ignore the members/buckets that don’t return a result because they can’t read the index, c

Re: [DISCUSS] Upgrading to Lucene 7.1.0

2021-09-28 Thread Nabarun Nag
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 test so that it does the query. Regards Naba _

Odg: [DISCUSS] Upgrading to Lucene 7.1.0

2021-09-28 Thread Mario Kevo
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 that Upgrading+to+Lucene+7.1.0. The first larger change was in the scorin