http://platinumdogs.me/2014/01/07/controlling-search-noderunner-memory-usage-in-sharepoint-2013/
Although it is tempting to reduce memory of node runner
Leave it at zero or adjust carefully as suggested above to 1 or 2 GB.
Somme errors that you might see:
Log Name: Application
Source: .NET Runtime
Date: 29.01.2015 11:43:59
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer:
Description:
Application: NodeRunner.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.OutOfMemoryException
Stack:
at System.Runtime.Fx+IOCompletionThunk.UnhandledExceptionFrame(UInt32, UInt32, System.Threading.NativeOverlapped*)
at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)
Log Name: Application
Source: Application Error
Date: 29.01.2015 11:43:59
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer:
Description:
Faulting application name: NodeRunner.exe, version: 15.0.4420.1017, time stamp: 0x506723c5
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x5315a05a
Exception code: 0xe0434352
Fault offset: 0x000000000000940d
Faulting process id: 0xe90
Faulting application start time: 0x01d03bb070ecf82a
Faulting application path: C:\Program Files\Microsoft Office Servers\15.0\Search\Runtime\1.0\NodeRunner.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: bae00371-a7a3-11e4-b181-00155dfe9e6f
UPDATE: the issue is back again. This article here talks about finding out which com ponent is using memory http://blogs.msdn.com/b/kristopherloranger/archive/2014/03/24/sharepoint-2013-noderunner-exe-process-information.aspx
No comments:
Post a Comment