locked
Mssearch.exe consuming High CPU over extended time period RRS feed

  • Question

  • Hello,
    We are running SQL 2000 sp4 with full text search, recently we are
    getting 100% CPU over extended period of time and the only way to
    resolve this is by killing the Mssearch.exe process. (we tried to
    restart the service but it hang) the Microsoft search service is
    running under local system account.
    our system topology is active/passive cluster with NAS disks, 4GB RAM
    and 4 CPU for each server.
    May be some one can help me???
    The issue happen randomly with no specific job running at that time or
    any thing, and when it happen the SQL queries are running very very
    slow.
    Thank you

    Tuesday, November 8, 2005 12:46 PM

Answers

  • I asked our dev team and there are no known problems of this kind. I would recommend contacting product support services and have them look at your particular configuration. Most likely the problem you are seeing is caused by the content being indexed.
    Thursday, November 17, 2005 10:12 PM

All replies

  • No solution to your particular problem, except looking at a prioir post:

    http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=93706&SiteID=1

    In your particular case, when did the problem start? After upgrade, some configuration change, resource change, database size change?

    This may help understand the problem.

    Thanks,
    Boris.
    Wednesday, November 16, 2005 6:56 PM
  • I asked our dev team and there are no known problems of this kind. I would recommend contacting product support services and have them look at your particular configuration. Most likely the problem you are seeing is caused by the content being indexed.
    Thursday, November 17, 2005 10:12 PM
  • Hi,

    We appear to be experiencing the same thing.  There is no disk activity - just mssearch running at 100% utilization.

    Have you found an answer yet?
    Tuesday, November 29, 2005 8:22 PM
  • We used Microsoft support and nothing found we tried rebuild all catalogs , Fix some snapshot problem on the NAS and still we got the same problem finally we changed the affinity mask of the Mssearch and the SQL (SQL use CPU 1 and 2 and Mssearch the rest) we are still waiting to see if it help to solve the problem for now (4 days) it look fine even though the Mssearch took 100% the SQL continue to give services and the CPU drop back to normal with out human interference. So I will have more clear answer with in a week.
    Wednesday, November 30, 2005 9:04 AM