When creating the Search Service application , a default topology will be built automatically where all Search components are assigned to the server which is running the Central Administration, in multi servers farm scenario you need to change this topology , the only available way currently is through PowerShell which will provide more flexibility in configuring the topology, (you can NOT modify the topology through UI like you used to do with SharePoint 2010)
I will guide you in this post on how to configure 5 servers as the following:
you can refer to the below diagram to have better understanding for the topology we are about to configure:
now let us start by opening the powerShell on the server running the Central administration, make sure to execute all the below commands in the same PowerShell screen, but I have divided them in below to make them more readable:
where SPAPP-SRV1, SPAPP-SRV2, SPWF-SRV1, SPWF-SRV2, SPWF-SRV3 are the server names
$hostApp1 = Get-SPEnterpriseSearchServiceInstance -Identity "SPAPP-SRV1"
$hostApp2 = Get-SPEnterpriseSearchServiceInstance -Identity "SPAPP-SRV2"
$hostWF1 = Get-SPEnterpriseSearchServiceInstance -Identity "SPWF-SRV1"
$hostWF2 = Get-SPEnterpriseSearchServiceInstance -Identity "SPWF-SRV2"
$hostWF3 = Get-SPEnterpriseSearchServiceInstance -Identity "SPWF-SRV3"
Start-SPEnterpriseSearchServiceInstance -Identity $hostApp1
Start-SPEnterpriseSearchServiceInstance -Identity $hostApp2
Start-SPEnterpriseSearchServiceInstance -Identity $hostWF1
Start-SPEnterpriseSearchServiceInstance -Identity $hostWF2
Start-SPEnterpriseSearchServiceInstance -Identity $hostWF3
Get Search Service Instance status (started or stopped) after running the above commands
$ssa = Get-SPEnterpriseSearchServiceApplication
$newTopology = New-SPEnterpriseSearchTopology -SearchApplication $ssa
New-SPEnterpriseSearchAdminComponent -SearchTopology $newTopology
New-SPEnterpriseSearchCrawlComponent -SearchTopology $newTopology
New-SPEnterpriseSearchContentProcessingComponent -SearchTopology $newTopology
New-SPEnterpriseSearchAnalyticsProcessingComponent -SearchTopology $newTopology
New-SPEnterpriseSearchIndexComponent -SearchTopology $newTopology
-SearchServiceInstance $hostApp1 -IndexPartition 0
-SearchServiceInstance $hostApp2 -IndexPartition 0
#SPWF-SRV1 , SPWF-SRV2 , SPWF-SRV3
New-SPEnterpriseSearchQueryProcessingComponent -SearchTopology $newTopology
#Activate the Topology
Set-SPEnterpriseSearchTopology -Identity $newTopology
# Verify the Topology
Get-SPEnterpriseSearchTopology -SearchApplication $ssa
Simply brilliant. Thanks for sharing.. You guys are quickly becoming my go to people in SharePoint farm administration..
Quick Question... I like to run SharePoint 2013 all search components on dedicated application servers including query components.. with new SP2013 guidance around streamlined topology, it is recommended to run both query and index on same server and avoid running on WFEs due to distributed catche. What do you think about that? Any opinions?
Hi Nik ,
glad you liked the post, well runnning the search components on a dedicated search servers is absolutely much better ... im my above post im assuming you dont have the luxury of having dedicated servers for search query processing, your assumption is correct to have query processing and Index on a seperate server together (if you can afford having more servers in your farm). :)
Thanks Issa.. that's exactly we are going for.. Thanks for reply..
All of the commands under the 'setting up the topology' section are truncated, rendering this post unusable.
you should see the full commands now... check it
I would also suggest to add some pre-requisites e.g. Search Service Application is already provisioned (which you already suggested in your pre-reqs but may not be obvious to many). Additionally, what search services (e.g. host controller, search settings, and server search services) are started on which server before running this command.. it would make it much clear for readers to see what are starting point...
Very useful information. Thank you
If anyone wants to look at SharePoint search 2013 architecture and configuration
can't get it to work...got one WFE and one APP....
Useful info to understand Search topology........ :)
thanks you very much, it is very clear and clean
I receive the "Sorry, something went wrong." when searching with details “The load balancer is not provisioned. Verify the load balancer was provisioned successfully before retrieving endpoint addresses.” I have re-created the Search Service Application
several times already without success. The crawler was able to crawl the sites showing successful crawls. I do not see any account permissions or access issues in DB event logs and nothing looks out of place in the web front end and application server event
logs also. I can see the full topology as well as all items in the search administration page. Prior to using the PowerShell code above to change the topology even when the Search Service Application was provisioned through the Central Administration with
all search components on one server, I still saw the same error message regarding the load balancer after crawling completed. I used four accounts and they do not have any admin privileges. They were all registered as managed accounts prior to provisioning.
In the ULS after the “UserAgent not available, file operations may not be optimized.” and a few other informational items, the most significant unexpected level is regarding the load balancer:
Getting user preference failed: System.InvalidOperationException: The load balancer is not provisioned. Verify the load balancer was provisioned successfully before retrieving endpoint addresses.
Any ideas on how to resolve this?