Udostępnij za pośrednictwem

SharePoint 2013 Preview – Hungry search service

  • Artykuł

Due to the many response I get: This post was written specifically for the Preview of SharePoint 2013
The memory leak is resolved in RTM. Please do not apply the memory settings in production!

 

Just today there was some discussion on our internal DLs about the noderunner.exe processes of the Enterprise Search service being very hungry for CPU and RAM.

It turns out that there is a memory leak and a lot of debug code involved [REMEMBER: We are still at beta here J].

Jose Vigenor from MS beta support pointed to two options to contain these processes:

  1. Use Set-SPEnterpriseSearchService -PerformanceLevel Reduced to reduce the CPU impact the search service has on your test environment.
  2. Modify the C:\Program Files\Microsoft Office Servers\15.0\Search\Runtime\1.0\noderunner.exe.config so that it can only consume X amount of RAM.
    Change the value at <nodeRunnerSettings memoryLimitMegabytes="0" /> to any amount of RAM you like to contain the memory leak.

Good luck!

Comments

  • Anonymous
    January 01, 2003
    Thanks for the tip, it's proved very handy to control the process on my dev machine. I did however hit a problem with the memoryLimitMegabytes when I was changing the search topology in PowerShell. Once I had cloned the topology, changed things around and then went to reactivate the topology, the script took about 10 minuts before it finally crashed out with the error "Failed to connect to System Manager" Unable to connect to system client with derived management URIs. Exception: Failed to connect to system manager. SystemManagerLocations: net.tcp://win2k8sp15/78580D/AdminComponent1/Management    at Microsoft.Office.Server.Search.Administration.SearchServiceApplication.GetSystemClient(IList`1 systemManagerLocations)     at Microsoft.Office.Server.Search.Administration.Topology.ApplicationAdminLayer.Reconnect() c80fcf9b-cf6b-2083-a27f-5d57c7dc4ef3 Deeper analysis of the ULS logs shows that the DBConnector created by the Noderunner process threw an OutofMemory exception. Removing the Noderunner.Exe.Config memory restriction and rebooting the server allowed me to submit the topology change. Paul.

  • Anonymous
    January 01, 2003
    The comment has been removed

  • Anonymous
    January 01, 2003
    The comment has been removed

  • Anonymous
    January 01, 2003
    Very good content.

  • Anonymous
    January 01, 2003
    The comment has been removed

  • Anonymous
    January 01, 2003
    RTM still memory hungry. I have 5 of noderunner.exe running with the total of 1.3GB of ram

  • Anonymous
    September 13, 2012
    Oh good to know!l  Yeah, as anything BETA it is subject to how much pain one can take..... I'll check this setting out! Cheers, Oscar

  • Anonymous
    September 19, 2012
    Thanks for the information. Much needed for my environment.

  • Anonymous
    September 25, 2012
    Is This <nodeRunnerSettings memoryLimitMegabytes="0" /> Bytes or KiloBytes or MegaBytes ? Thanks Nigel

  • Anonymous
    September 25, 2012
    Forget last comment - I cannot read !!

  • Anonymous
    March 26, 2014
    Hello Anonymous,
    I have the same after SP1: all application uses 8GB of 16GB Ram and noderunner.exe chrashes each 20 seconds with OutOfMemoryException
    And Search web app doesn't work any more :-(

  • Anonymous
    April 11, 2014
    we have the same issue, rebooting the server works for a wile, right now the server already has 16 GB of memory but it just keeps eating more and more.

  • Anonymous
    April 10, 2015
    The comment has been removed