Service Application

full crawl takes too long to complete sharepoint search

I faced an issue with sharepoint search where full crawl takes too long to complete nearly 240 hours. Requirement was how to reduce the full crawl time.

Advertisements

Service Applications in SharePoint

Service Applications in SharePoint are associated with web applications, and specific services are typically deployed as needed in a particular farm. Only deployed services are referred to as service applications. This is a huge advantage in terms of conserving resources and optimizing performance. For instance, a specific web application can be configured to use only the services it needs. The number of service applications that exist is vast, and, as third-party vendors can create their own services for SharePoint Server. A list of services includes the following:

SharePoint search crawl properties storage locations

When gathering files from a content source, the SharePoint 2013 Crawl Component can be very I/O intensive process – locally writing all of the files it gathers from content repositories to its to temporary file paths and having them read by the Content Processing Component during document parsing. This post can help you understand where the Crawl Components write temporary files, which can help in planning and performance troubleshooting (e.g. Why does disk performance of my C:\ drive get so bad – or worse, fill up – when I start a large crawl?)

Query 0 Server Not Responding – Event ID 2587

Failure Message Object Query-0 (D: on SERVER1) failed in event On Backup, Index Partition – 0 – SERVER2Search_Service_Application_PropertyStoreDB_9a482efd99954748a062952a3d2617d7, Query Component 0 SERVER1 Not Responding, Event ID 2587, The following conditions are currently affecting index propagation to this server for search service application ‘Search Service Application’, Query 0, catalog Main: failing to copy index files from crawl component 0 for 1490 minutes. Access is denied. 0x80070005, Query 0 is not being automatically disabled because the minimum number of ready query components per partition is 2