Indexer Crashed on 4.2a Upgrade

Richard DeRuiter said:

The command is rebuild index. The problem in your logs seems to be in merging the regular index with the supplemental index. Rebuilding the index should fix this. It will probably also take a long time to finish.

It was my understanding from Melissa's post that the index would be automatically rebuilt after the download completed. Given the actions I saw when my system updated that does seem to be the case. Am I missing something here?

Joe said:

Thanks....!  So, I have a multi-core processor.  Will it slow everything down?  Or simply take up one core?  i.e. if it slows everything down, then I may just do it overnight after I leave work.  If it just takes up one core, I can just use Logos while I'm working throughout the day and do my other stuff.

Joe

I have a quad core processor and my system used all four cores while it was indexing. Utilization for each core flucuated between 10% and 80 %. It took about an hour to complete the index rebuild on my system.

Richard DeRuiter said:

Yes, it does re-index. However, in this case (and maybe every case) it appears to try to merge the regular and supplemental indexes. This is where the problem occurred according to the log. By rebuilding the index you effectively destroy both indexes and force a full rebuild of the primary (regular) index.

Forgive me if I am quibbling over semantics Richard, but Melissa specifically states it will Rebuild the index after completing the upgrade the first time the software is started. And my system typically only takes a few miniutes to merge indexes with only moderate CPU utilization. . In this instance it took an hour with heavy CPU usage. I am not saying you are incorrect but i am looking for clarification.

Richard DeRuiter said:

However, looking at the logs above, the issue occurred when this opperation was running:

Info    BibleIndex    Merging indexes 'index' and 'supplemental' into index in C:\Users\Joe\AppData\Local\Logos4\Data\i5sx3pvq.qvu\BibleIndex

The error on the next line, which is in the same process thread (8) says "Unable to merge non-skiplist index with skiplist index."

While I have no idea what a "skiplist" is, the thread/error together looks to me like a problem merging to indexes.

I understand where you are coming from now Richard. Thank you for taking the time to explain.

Blessings,

Bob

Joe said:

Just re-indexed the entire thing and it only took about an hour for me as well!

Thanks everyone!!   

Joe

You are very welcome Joe.

I executed the command "rebuild index" just to confirm what I suspected and it took the same length of time as the initial rebuild after upgrading. So the software is doing a complete rebuild once the upgrade has finished.

Blessings,

Bob

Richard DeRuiter said:

The error on the next line, which is in the same process thread (8) says "Unable to merge non-skiplist index with skiplist index."

This will be fixed in 4.2a SR-1 which will be released today, so that users who are still crashing, or users who haven't updated yet, won't continue to get this crash.