Title: I use FAST Search and my TeamPage server has suddenly become very slow or has reported OutOfMemory errors. How do I recover?
If you have recently rebooted the computer hosting your FAST installation without giving FAST a chance to shut down completely, chances are that you that your FAST statusserver database must be recovered. Until this happens, FAST feeding from Traction may not operate properly, causing Traction's memory to be exhausted. Symptoms of this problem include:
• Normally long-running, stable Traction servers become very sluggish and run out of memory in a very short period of time. The memory graph you generate from Support668 will flatline, like the memory starvation example in the graph below.
• The system has been rebooted recently.
• New documents are not being indexed by FAST search, and appear in the needs column of the FAST Index Administration page and never move to the pending or complete status.
• The FAST InStream admin interface reports 0 documents in the collection.
Resolving this problem is straightforward: you need to kill all instances of the statusserver.exe process using the Windows Task Manager (on Unix you should kill -9 the statusserver processes owned by the FAST user).
This puts the FAST status server into "recovery mode", which rebuilds the status database. Once this has completed, you should restart your TeamPage server. Indexing should then resume, with normal memory utilization and performance.
