[Building Sakai] still struggling with indexer errors

Joshua Swink joshua.swink at gmail.com
Thu Oct 28 14:01:29 PDT 2010


We're still struggling with the indexer errors that say "no segments*
file found", as in the ticket
http://jira.sakaiproject.org/browse/SRCH-15. I'm just throwing this
out there in the hope that someone familiar with the code or the
configuration of the search tool may have some idea of how to correct
this.

Our last effort to fix this was as follows:

* Verify that sharedJournalBase at org.sakaiproject.search.api.JournalSettings
pointed to a shared location that all tomcat instances have read/write
access to.
* Verify that localIndexBase at org.sakaiproject.search.api.JournalSettings
points to a local location for each tomcat instance, which is not
shared.
* Shut down all Tomcat instances, then:
** Erase the contents of the sharedJournalBase directory.
** Erase the contents of all search tables in the database:
search_journal, search_node_status, search_segments,
search_transaction, searchbuilderitem, and searchwriterlock.

After starting Sakai up again, the errors continue, on all instances.
Also note that search does not work - any attempt to perform a search
generates a similar error. The search indexer is constantly hitting
the database pretty hard, making up the bulk of the database load for
Sakai.

Josh


More information about the sakai-dev mailing list