[Building Sakai] still struggling with indexer errors

[Joshua Swink]

The errors start during startup. So I'm not fully clearing the index?

Josh

On Fri, Oct 29, 2010 at 12:32 AM, David Horwitz <david.horwitz at uct.ac.za> wrote:
> Hi Joshua,
>
> Do you get the error immediately after start-up or after running for a
> while? If the former then you haven't cleared the index (the list bellow
> doesn't include clearing the local index files that it should) If this
> is happening after the index has been running for a while then it is
> likely that one of a couple of things is happening:
>
> 1) an error (like running out of disk space) happened during an index
> maintenance operation on that node
> 2) The restart of a node left it out of synch with the shared index (in
> which case you can delete the local index files on that node and let  it
> reload from shared)
>
> D
>
> On 10/28/2010 11:01 PM, Joshua Swink wrote:
>> 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
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>