SharePoint 2013 Search Service: Primary and Replica Index different size (and high index component ratio) - Fabian Neve

About SharePoint, Javascript, PowerShell, and other technical stuff

Thursday, November 5, 2015

SharePoint 2013 Search Service: Primary and Replica Index different size (and high index component ratio)

I had an issue, where the index size on two server were very different. While the primary and replica index on WFE1 used 136 GB together, the size on WFE2 was only about 57 GB.


With an Index Report PowerShell script (which I found here: MSDN Blogs > SharePoint Strategery > Examples Using SP2013 Search Index health reports for monitoring and troubleshooting) I could see a very high Index Ratio of about 61% (Target is about 10%).


The root cause

...could be, that the disk on one WFE was at one time very full (0 MB free space), maybe this was the cause why merging didn't work properly.

The Solution

I did full crawls on my content sources, but no effect. Only a complete index reset followed by a full crawl on every content source did the job. After some time, my ratio was about 7.5 %.

Maybe more solutions will be posted in my corresponding thread on Stackexchange.

Epilogue

I'm very excited about this SP Index Report PowerShell Script. You only have to run this CMD-let and script and you get a whole report about the health of your search index:

Import-Module "D:\Tools\Scripts\Get-SPIndexReports-v1.2.psm1"

Get-SPIndexReports -Detailed

Feel free to leave a comment. :-)

No comments:

Post a Comment