locked
fixmlindex.exe process running with high memory and cpu RRS feed

  • Question

  • The following link mentions a workaround for when the fixmlindex.exe process is running with high memory.


    http://office.microsoft.com/en-us/search-server-help/microsoft-search-server-2010-and-microsoft-fast-search-server-2010-known-issues-readme-HA101793221.aspx

    The steps noted in the above link:

    1.Perform all schema updates before starting feeding.
    2.Stop the FASTSearchService
    3.Remove the file
    4.etc\config_data\Schema\webcluster\summaryclasses.xml
    5.Start the FASTSearchService
     

    My questions:
    a.  By schema updates are they referring to all the tweaks in SharePoint Search Admin/Metadata
    b.  What is the summaryclasses.xml file - does this file get created on first full crawl, and then updated when the schema changes
    c.  Should I perform a full crawl after such changes?

    d. What the heck is fixmlindex.exe purpose

    Sunday, August 14, 2011 2:01 AM

Answers

  • Hello nayr,

    a) Schema updates are any changes to a managed property(create,remove,change props), or change to the fulltext schema and rank profiles. So, yes, some of the tweaks on metadata in FAST search admin.

    b) summaryclasses.xml is a run-time file which is derived from the index configuration, and contains the managed properties set in your system as well as internal FAST properties. Removing this file will ensure it is being re-generated.

    c) As point 1) says, apply updates before feeding. This implies clearing the collection on the FAST side, and doing a index reset on the Content SSA. It is good practice to try before you go live and create all the managed properties you need before you start indexing, to limit re-indexing afterwards.

    d) When content is indexed in FAST and has run thru the document processor pipeline, it generated intermediate xml files, in an internal FAST format called FiXML. You can find these files below your <FASTSearchFolder>\data\data_fixml folder with the extension .gz. You can gunzip them and have a peek. The FiXML files are then sent with the indexing dispatcher to the indexer process(s) to create the binary index used during searching.

    Hope this explains it a bit :)

    Regards,
    Mikael Svenson 


    Search Enthusiast - SharePoint MVP/WCF4/ASP.Net4
    http://techmikael.blogspot.com/
    • Proposed as answer by Thomas Svensen Monday, August 15, 2011 6:52 AM
    • Marked as answer by nayr Monday, August 15, 2011 12:04 PM
    Sunday, August 14, 2011 6:30 PM

All replies

  • Hello nayr,

    a) Schema updates are any changes to a managed property(create,remove,change props), or change to the fulltext schema and rank profiles. So, yes, some of the tweaks on metadata in FAST search admin.

    b) summaryclasses.xml is a run-time file which is derived from the index configuration, and contains the managed properties set in your system as well as internal FAST properties. Removing this file will ensure it is being re-generated.

    c) As point 1) says, apply updates before feeding. This implies clearing the collection on the FAST side, and doing a index reset on the Content SSA. It is good practice to try before you go live and create all the managed properties you need before you start indexing, to limit re-indexing afterwards.

    d) When content is indexed in FAST and has run thru the document processor pipeline, it generated intermediate xml files, in an internal FAST format called FiXML. You can find these files below your <FASTSearchFolder>\data\data_fixml folder with the extension .gz. You can gunzip them and have a peek. The FiXML files are then sent with the indexing dispatcher to the indexer process(s) to create the binary index used during searching.

    Hope this explains it a bit :)

    Regards,
    Mikael Svenson 


    Search Enthusiast - SharePoint MVP/WCF4/ASP.Net4
    http://techmikael.blogspot.com/
    • Proposed as answer by Thomas Svensen Monday, August 15, 2011 6:52 AM
    • Marked as answer by nayr Monday, August 15, 2011 12:04 PM
    Sunday, August 14, 2011 6:30 PM
  • I deleted summaryclasses.xml and ran into some problems.... The issues did not occur until I tried to add new metadata properties. See this thread for more:

    http://social.technet.microsoft.com/Forums/en-US/fastsharepoint/thread/e3f1f7ee-9f82-40fa-940c-58039a08cf24

    Thursday, July 19, 2012 9:10 PM
  • Hi Nayr,

    What are the steps to perform schema updates?

    Thanks,

    Ashish Dubey

    Sunday, January 31, 2016 2:20 PM