Issue during search index component movement + SharePoint

Issue : Command Set-SPEnterpriseSearchTopology -Identity $Clone is stuck and endless running.

Analysis : We see the topology is changed successfully from OWS Timer category of ULS log . So we performed some basic checking, it looks like everything is running fine and is healthy.  It sounds like that the timer job doesn’t signal the PowerShell process when activating is finished. So looks like the communication issue between timer job and powershell process. So we decide to turn all timer service off from all the other servers other than the admin component server and the new component server. And it is working well. Later, we start all the timer service again. Running the script again, all are working fine. So the only difference compared with fail scenario is that the restarting of the timer service. Hence we have a solution below.

Solution :

1. Restart all timer service for all servers.

2. Then using below command to verify its status

 

$farm  = Get-SPFarm

$disabledTimers = $farm.TimerService.Instances | where {$_.Status -ne "Online"}

if ($disabledTimers -ne $null)

{

    foreach ($timer in $disabledTimers)

    {

        Write-Host "Timer service instance on server " $timer.Server.Name " is not Online. Current status:" $timer.Status

        Write-Host "Attempting to set the status of the service instance to online"

        $timer.Status = [Microsoft.SharePoint.Administration.SPObjectStatus]::Online

        $timer.Update()

    }

}

else

{

   Write-Host "All Timer Service Instances in the farm are online! No problems found"

}