I normally run an optimize to 16 segments after each major indexing
period. Much more than that and the nodes "drag". Waiting on last
collection to finished optimizing to 1 segment before trying again.
On 10/6/21 1:56 PM, Dave wrote:
It’s ok. Worst case it just fails and kills the temporary index after you run
out of space. Really optimize is almost not even supported (it still works) but
a full reindex is always the best bet if you can destroy original and it
doesn’t effect anything
On Oct 6, 2021, at 1:53 PM, Michael Conrad <mich...@newsrx.com> wrote:
too late.... it's in progress.
On 10/6/21 9:11 AM, Dave wrote:
Hold on that idea then. An optimize will use three times your index size
possibly.
On Oct 6, 2021, at 9:02 AM, Michael Conrad <mich...@newsrx.com> wrote:
Thanks,
I think we'll try the full optimize route as we don't have storage to spare for
second copies, etc.
-Mike
On 10/6/21 8:54 AM, Dave wrote:
Personally I always do a full reindex when going to a new version, just safer
and you should always be able to do such at any point. However if you got the
time to spare you can do an optimize and it will force the segments all into
the current version
On Oct 6, 2021, at 8:46 AM, Michael Conrad <mich...@newsrx.com> wrote:
Hello all,
Is there an easy way to determine Lucene versions for segments?
If we were to do a full reindex, rewriting all segments, would that update the
segment version to match the current Lucene version in use?
We are working on upgrading from Solr 7.7.3 to Solr 8.x but have discovered
that several of our collections have segments that are Lucene 6.
-Mike
