Extend content capacity for an existing deployment (FAST Search Server 2010 for SharePoint)(informazioni in lingua inglese)

Data pubblicazione: 16 dicembre 2010

A default Microsoft FAST Search Server 2010 for SharePoint indexer configuration is optimized for content volumes up to 15 million items per index column. You can change the indexer configuration to handle up to 40 million items per column.

Avviso

Before you change the configuration, you must first remove all indexed content from your FAST Search Server 2010 for SharePoint farm. Depending on the size of your deployment, it may take days or even weeks to re-index the content.

Before you extend the content capacity, read the Performance aspects and hardware recommendations.

To extend content capacity for a deployment with indexed content

  1. Stop crawling.

  2. Pause the Web Analyzer components. These components analyze links between items and search clickthrough logs. The components must be stopped to avoid partial updates for indexed items during the procedure.

    1. On the administration server, open a FAST Search Server 2010 for SharePoint shell.

      1. Verify that you meet the following minimum requirements: You are a member of the FASTSearchAdministrators local group on the server where FAST Search Server 2010 for SharePoint is installed.

      2. On the Start menu, click All Programs.

      3. Click Microsoft FAST Search Server 2010 for SharePoint.

      4. Click Microsoft FAST Search Server 2010 for SharePoint shell.

    2. At the Windows PowerShell command prompt, type the following command:

      waadmin ShowStatus
      

      Nota

      Refer to waadmin.exe reference(informazioni in lingua inglese) if you are using multiple views for the Web Analyzer.

      In the Views section of the command output, for the default view, inspect the Schedule status.

      1. If the Schedule status is set to paused, type the following command:

        waadmin enqueueview
        
      2. Wait until the default Web Analyzer view is running. Type the command waadmin ShowStatus and inspect the Schedule status. The Schedule status should be set to running.

    3. At the Windows PowerShell command prompt, type the following command(s):

      waadmin AbortProcessing
      spreladmin AbortProcessing
      
  3. Wait until all item processing is finished:

    At the Windows PowerShell command prompt, type the following command:

    psctrl status
    

    Nota

    All processor servers must report "idle" before you proceed to the next step.

  4. Remove all items from the content index:

    1. If you are using the FAST Search Content SSA to crawl content, follow the steps in Reset the content index (FAST Search Server 2010 for SharePoint)(informazioni in lingua inglese) to remove all items from the default content collection named "sp".

    2. If you are using one or more of the FAST Search specific connectors to crawl content, remove all items from the content collections that are associated with these connectors.

      1. On the administration server, at the Windows PowerShell command prompt, type the following command(s):

        Get-FASTSearchContentCollection
        

        This will retrieve a list of all content collections.

      2. For each content collection, at the Windows PowerShell command prompt, type the following command(s):

        Clear-FASTSearchContentCollection -Name <ContentCollectionName> 
        

        Where <ContentCollectionName> is the name of the content collection.

  5. Make sure that no items are indexed on any of the indexers:

    On the administration server, at the Windows PowerShell command prompt, type the following command:

    indexerinfo –a doccount
    

    Nota

    All indexers must report 0 items before you proceed to the next step.

  6. Change the index partition configuration:

    1. On the administration server, locate the indexer template configuration file:

      <FASTSearchFolder>\META\config\profiles\default\templates\installer\etc\config_data\RTSearch\clusterfiles\rtsearchrc.xml.win32.template

      Where <FASTSearchFolder> is the path of the folder where you have installed FAST Search Server 2010 for SharePoint, for example C:\FASTSearch.

    2. Save a backup of the file. You may need the backup at a later stage if the configuration file is modified in a software update.

    3. In a text editor, open the file and change the following configuration parameters:

      • numberPartitions:

        Default value: 5

        New value: 10

      • docsDistributionMax:

        Default value:

        6000000,6000000,6000000,6000000,6000000

        New value:

        6000000,6000000,6000000,6000000,6000000,6000000,6000000,6000000,6000000,6000000

  7. Re-deploy the farm configuration to all servers:

    Gg482016.Important(it-it,office.14).gifImportante:
    In this step, you must change the deployment configuration file (deployment.xml) without changing the actual content. You can do that by adding a space and then save the file.

    Follow the steps in Reconfigure the farm deployment including adding new servers.

  8. On the administration server, at the Windows PowerShell command prompt, run the following commands to resume processing for the Web Analyzer components:

    waadmin EnqueueView
    spreladmin Enqueue
    
  9. Start a full crawl of all content:

Vedere anche

Concetti

About extended content capacity (FAST Search Server 2010 for SharePoint)(informazioni in lingua inglese)
Extend content capacity for a new deployment (FAST Search Server 2010 for SharePoint)(informazioni in lingua inglese)
Handle software updates when you have extended the content capacity (FAST Search Server 2010 for SharePoint)(informazioni in lingua inglese)
Plan FAST Search Server farm topology (FAST Search Server 2010 for SharePoint)(informazioni in lingua inglese)
Manage FAST Search Server farm topology (FAST Search Server 2010 for SharePoint)(informazioni in lingua inglese)
Add an index column (FAST Search Server 2010 for SharePoint)(informazioni in lingua inglese)

Altre risorse

FAST Search Server 2010 for SharePoint Capacity Planning (white paper)

Cronologia delle modifiche

Data Descrizione Motivo

16 dicembre 2010

Pubblicazione iniziale