SharePoint 2013 : Search service overall state: Degraded

Question

Hello Experts,

Need your help to figure this out, the search status report is showing "Search service overall state: Degraded " ? Every thing is fine. crawl is optimal, newly uploaded documents are searchable but when I run the famous Get-SPFarmInfo.ps1 to check the search status, I get this Degraded at the end of the script.
Degraded can be due to the warning towards the end of the script output as shown in italic below but not sure which timer jobs its complaining about. Any help will be appreciated.

Analytics Processing Job Status:
SearchAnalytics : Idle
Last successful start time: 6/25/2015 12:00:03 AM
Warning: More than three days since last successful run
Last completed time: 6/25/2015 1:12:59 AM
Last failed time: 4/24/2015 11:50:44 PM
Next scheduled run time: 6/25/2015 2:00:04 AM
UsageAnalytics : Idle
Last successful start time: 6/25/2015 1:00:00 AM
Warning: More than three days since last successful run
Last completed time: 6/25/2015 1:18:48 AM
Last failed time: 4/25/2015 1:30:28 AM
SearchReports : Idle
Last successful start time: 6/24/2015 9:10:01 PM
Warning: More than three days since last successful run
Last completed time: 6/24/2015 9:10:51 PM
Next scheduled run time: 6/24/2015 11:10:01 PM

I see a solution here but what timer job exactly we need that is not running from the last few days and causing this warning ?
https://social.technet.microsoft.com/Forums/en-US/bee91ee6-d6a2-40f3-b8c8-0e128090a26f/sharepoint-2013-search-timer-job-missing-and-not-running?forum=sharepointsearch

Both of these command return nothing: but that is same in all our farms.
Get-SPTimerJob -Type Microsoft.Office.Server.Search.Analytics.AnalyticsJobDefinition
get-sptimerjob -type microsoft.office.server.search.analytics.usageanalyticsjobdefinition

Thanks.

Answer 1

Hi @Umr ,

As per my knowledge, the same kind of timer job does not have to be available on all servers, right? All search components are healthy in your farm, the search functionality is working normally. I think you can ignore this problem since there are no specific errors in your farm.

---

If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.