Ask Learn
Preview
Ask Learn is an AI assistant that can answer questions, clarify concepts, and define terms using trusted Microsoft documentation.
Please sign in to use Ask Learn.
Sign inThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
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?)
By default, all Search data files will be written within the Installation Path
The Data Directory (by default, a sub-directory of the Installation Path) specifies the path for all Search data files including those used by I/O intensive components (Crawl, Analytics, and Index Components)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\15.0\Search\Setup\DataDirectory
(As a side note: the graphic is only intended to display the default locations specified at install time. It is recommended to change these to a file path other than C:\ drive)
For the Crawl Component:
In the registry (of a Crawl server)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\15.0\Search\Global\Gathering Manager\TempPath
Or as a property of the SSA:
$SSA = Get-SPEnterpriseSearchServiceApplication
$SSA.TempPath
In the graphic below, this occurs in step 2b
The defined path can be viewed in the registry (of a Crawl server):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\15.0\Search\Components\-GUID-of-theSSA-crawl-0\GathererDataPath
The shared path can be viewed in the registry (of a Crawl server):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\15.0\Search\Components\-GUID-of-theSSA-crawl-0\GathererDataShare
Usage by the Content Processing Components:
An example path to an item with DocID 933112 would look like the following:
file: //crawlSrv/gthrsvc_ 7ecdbb10-3c86-4298-ab09-04f61aaeb636 -crawl-0//f8/0xe3cf8_1.aspx
#0xe3cf8 hex = 933112 decimal
Where:
This GUID can be identified using the following PowerShell:
$SSA = Get-SPEnterpriseSearchServiceApplication
$searchAdminWeb = Get-SPServiceApplication –Name $SSA.id
$searchAdminWeb.id
7ecdbb10-3c86-4298-ab09-04f61aaeb636
From the Crawl Component (in this case, running on server "faceman"):
mssearch.exe SharePoint Server Search Crawler:Content Plugin af7zf VerboseEx
CTSDocument: FeedingDocument: properties : strDocID = ssic://933112 key = path values = \\FACEMAN\gthrsvc_7ecdbb10-3c86-4298-ab09-04f61aaeb636-crawl-0\\f8\0xe3cf8.aspx
From the Content Processing Component:
NodeRunnerContent2-834ebb1f-009 Search Document Parsing ai3ef VerboseEx
AttachDocParser - Parsing: 'file: //faceman/gthrsvc_7ecdbb10-3c86-4298-ab09-04f61aaeb636-crawl-0//f8/0xe3cf8.aspx'
I hope this help…
Ask Learn is an AI assistant that can answer questions, clarify concepts, and define terms using trusted Microsoft documentation.
Please sign in to use Ask Learn.
Sign in