SharePoint 2013: solves the problem of network crawling errors

Symptom:

Previously, the normal network crawling was suddenly unable to be completed, and it was always stuck when it reached a certain part.

 

Investigation:

This error is found after you view the log file.

11:14:51. 86 NodeRunnerQuery1-734f5ee7-2cc2-(0x0dd4) 0x14a0 search common processing 28 information component and system = Query1-734f5ee7-2cc2-4f18-bd98-65b4b94d6e02, correlation id = b4e09d9c-d3b3-f018-348e-8ecd7c7d551d, tenant id = 00000000-0000-0000-0000-000000000000 error code = 0, flow name = Microsoft. extends pointsearchproviderflow, Operator name = parserexecutor, message = the processing of item fails with error cannot plan query for index system sp122e3c9ebf29. index fragment '0' has no available cells. cell statuses: [Cell I .0.0 on node indexcomponent1: cell status service not injected (cell down or no fsindex query service)] b4e09d9c-d3b3-f018-348e-8ecd7c7d551d

 

Google found this article:

Http://www.thesysadminhimself.com/2013/08/sharepoint-search-index-partition-degraded.html (may need to flip the wall), found the cause is the index component and the partition is degraded

 

Solution:

Index reset, and then perform a full-network crawling. Reset operations such as (directly use the pictures of the buddy ):