In this post, we’re going to overview the components in SharePoint 2013’s Search Topology which can be very complex to configure. Here you will also find an overview and some useful instructions on how to configure, monitor and document them.
Search Topology Components
In SharePoint 2013, there are numerous components in Search Topology:
- Search Admin Component
- Content Processor
- Analytics Processor
- Query Processor
As you can see, Search Topology in SharePoint 2013 is complex. So is its configuration – but if you understand the basics it gets much easier and simpler.
First of all, let’s see an example. On the screenshot below, you can see the Search Topology of a customer of mine:
In this environment, we have five servers: two Applications, one Index and two Front-Ends. We assigned the following rules to each:
- Both App Servers are configured to be Search Admins.
- The Index Server has the Crawler, Content Processing and Analytics Processing roles.
- The primary App server and both Front-End servers are responsible for Query Processing.
- Index server and both Front-End servers store a replica of the index.
The current topology is always displayed on the Search Service Application in Central Administration, although the configuration can be done via PowerShell only.
Steps for achieving the Topology changes above:
- Add a new Index Component
- Add a new Crawl Component
- Add a new Content Processing Component
- Add a new Analytics Component
- Add a new Admin Component
For each of these steps, we have to clone the current Search Topology, add the proper component(s) and then activate the cloned topology. With these steps, we always have one active topology, although we might have multiple inactive topologies too, and can activate any of them at any time. This can be very helpful when doing performance tests, for example.
The best step-by-step on Search Topology configuration has been written by Steve Mann on his blog.
Due to the complexity of Search Topology in SharePoint 2013, its monitoring is essential in any environment. Let’s see what options we have:
- Health information on the Search Service Application for Search Topology components. It gives us information on each component by color-coding (green – yellow – red).
- The PowerShell command Get-SPEnterpriseSearchStatus provides more details, including detailed diagnostic information for quick troubleshooting.
- We have Search Health Reports in Search Administration / Diagnostic, where we can check the performance and health of each component. Some reports here: Query Performance, Query Latency, Crawl Rate, etc.
If you’re a Search Admin, it’s better to add checking the health of the Search Components to your daily routine, preferably in the mornings. As seen, you can do this by visiting the SSA on the Central Administration or by PowerShell. The best way, of course, is to use a scheduled job to check the status of each component and send an alert if something is degraded or failed.
Documenting Search Topology
Documenting the configuration steps and the final topology has always been a challenge. But with the help of Documentation Toolkit for SharePoint, it gets easier than ever – let me show you how.
The latest version of the Toolkit contains a great feature for documenting Search topology. For example, let’s say my farm consists of the following five servers:
The following screenshot shows what the SP Documentation Toolkit sees, including:
- the initial, one-server search topology as an inactive one (Topology #1).
- the final, active topology, which consists of five servers (Topology #14).
- each inactive topologies, which have been created during the incremental configuration (Topology #2 – Topology #13).
Want to read more posts from us? Subscribe to our blog and stay updated!