Restart-SPEnterpriseSearchQueryComponent

 

Applies to: SharePoint Server 2010

Topic Last Modified: 2016-11-14

Restarts a failed query component.

Syntax

Restart-SPEnterpriseSearchQueryComponent [-Identity] <QueryComponentPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-QueryTopology <QueryTopologyPipeBind>] [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf [<SwitchParameter>]]

Detailed Description

The Restart-SPEnterpriseSearchQueryComponent cmdlet recovers a failed query component from its redundant component under the same index partition. There must be redundant query components (at least two) serving one index partition, one of which being in Ready state.

If this query component is offline because of some failures —for example, index corruption, low disk, or out-of- sync — a user can recover this component by running this cmdlet.

Note

Although the Restart-SPEnterpriseSearchQueryComponent cmdlet is designed to recover a failed (offline) query component, it can also be called on a Ready component to clone one that has the same index files as its source component.

Parameters

Parameter	Required	Type	Description
Identity	Required	Microsoft.Office.Server.Search.Cmdlet.QueryComponentPipeBind	Specifies the query component to restart. The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh, or an instance of a valid QueryComponent object.
AssignmentCollection	Optional	Microsoft.SharePoint.PowerShell.SPAssignmentCollection	Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used. Note When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur.
Confirm	Optional	System.Management.Automation.SwitchParameter	Prompts you for confirmation before executing the command. For more information, type the following command: get-help about_commonparameters
QueryTopology	Optional	Microsoft.Office.Server.Search.Cmdlet.QueryTopologyPipeBind	Specifies the query topology that contains the query component collection. The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh, or an instance of a valid QueryTopology object.
SearchApplication	Optional	Microsoft.Office.Server.Search.Cmdlet.SearchServiceApplicationPipeBind	Specifies the search application that contains the query topology. The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid search application name (for example, SearchApp1); or an instance of a valid SearchServiceApplication object.
WhatIf	Optional	System.Management.Automation.SwitchParameter	Displays a message that describes the effect of the command instead of executing the command. For more information, type the following command: get-help about_commonparameters

Input Types

Return Types

Example

------------------EXAMPLE------------------

$ssa = Get-SPEnterpriseSearchServiceApplication -Identity MySSA
$qt = $ssa.QueryTopologies
$qc = Get-SPEnterpriseSearchQueryComponent -QueryTopology $qt.ActiveTopology
$qc | fl Name,State

Name  : 06f80fa2-c043-41cf-9b73-1c86037be74e-query-1
State : Ready

Name  : 06f80fa2-c043-41cf-9b73-1c86037be74e-query-0
State : Offline

$qc[0] |  Restart-SPEnterpriseSearchQueryComponent

This example restarts a query component in the active query topology of a search service application named MySSA.