While running incremental crawl on sharepoint I am getting below event id every 10 seconds.
Event Type: Information Event Source: Windows SharePoint Services 3 Search Event Category: Gatherer Event ID: 2478 Date: 27/09/2010 Time: 12:27:22 User: N/A Computer: PANAAMA Description: The search service stopped the filter daemon because it was consuming too many resources. A new daemon will automatically be started, and no user action is required.
The tastes folks available simply do not have two freezers, an unfinished basement to convert to a home fitness space or unlimited hours inside day to pursue their fat loss neither did we. Only should you want to create your how to lose weight easily online. Do not turn about the television and sink into the couch immediately after dinner.
Commented By: Cecilia
Thanks Topman, I did the chnages and now I do not see the event log message anymore.
Commented By: Topman
I found this very good notes that can help.
IFilter Issues - the Adobe PDF IFilter can only filter one file at a time and that will slow crawls down, and has a high reject rate for new PDFs Solution: Use a retail PDF filter from pdflib.com or Foxit Not enought Memory Allocated to Filter Process - an aspect of the crawling process is then the filtering deamons use up to much memory (mssdmn.exe) they get automatically terminated and restarted. There is of course a windup time when this happend and can slow down your crawling. The current default setting is pretty low (around 100M) so is easy to trip when filter large files. You can and should increase the memory allocation by adjusting the following registry keys HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Global\Gathering Manager: set DedicatedFilterProcessMemoryQuota = 200000000 Decimal HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Global\Gathering Manager: set FilterProcessMemoryQuota = 200000000 Decimal Bad File Retries - there is a setting in the registry that controls the number of times a file is retried on error. This will severly slow down incremental crawls as the default is 100. This retry count can be adjust by this key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Global\Gathering Manager: set DeleteOnErrorInterval = 4 Decimal
General Architecture Issues - Ensure that you have at least 2 Gig of free memory available before your crawl even starts and that you have at least 2 real processors available.