[Deploying Sakai] Unhelpful error messages from search

Adams, David da1 at vt.edu
Thu May 21 05:34:39 PDT 2009

We recently did a reconfiguration of our Sakai deployment and when we
brought things back up, we noticed a lot of messages in the log from
r. Every ten seconds, it says:

ERROR: This node already merging shared segments, index writer
ketchup:1242477119395   This node is currently optimizing the shared
segments,      This is an error as only one copy of this node should be
Active in the cluster

Looking at the error in the source (DbJournalOptimizationManager.java in
search-impl) isn't any more helpful, but I did look at the table that is
triggering this message, SEARCH_JOURNAL, and we have 51 entries with
status 'merging-prepare' with indexwriter "ketchup:1242477119395" and
795 entries with status 'committed' and indexwriter "ketchup".

I haven't looked any deeper yet, but I am suspecting this is just a
matter of the database getting out of sync with reality for whatever
reason. Does anyone have any tips on safe ways to try to address
whatever the issue is? Or pointers to useful resources on understanding
how search works? I'm not sure what information in the wiki is reliable.
We're on the 2.5.4 tag if it makes a difference.

David Adams
Director of Learning Systems Integration and Support
Virginia Tech Learning Technologies

More information about the production mailing list