question

AdamTyler-3751 avatar image
0 Votes"
AdamTyler-3751 asked YukiSun-MSFT edited

Exchange 2016 outage this morning

We experienced an Exchange outage this morning with our on-prem stand alone Exchange 2016 server. After investigating, this appears to be a resource issue. Here are some screenshots collected during the disruption. Main issue is that Outlook clients were temporarily unable to connect. Problem seemed to resolve itself after a few minutes, but many users impacted.

See this related article I posted a while back discussing how resources should be allocated and for a bit more info on our environment:
https://docs.microsoft.com/en-us/answers/questions/474373/exchange-2016-resources-and-constant-msexchangeaut.html

Screenshots collected during outage...
125132-image.png


125089-image.png


I did allocate an additional 4GB of RAM to this ESXi based Exchange server VM and this is what resources look like now. I used the hot add memory feature, so the server was never rebooted. Confirmed it recognizes the 24Gb RAM now where it had 20 before. I'm curious what would make the noderunner.exe processes go a bit nuts with CPU resources and now be totally quiet. There aren't any mailbox moves going on or anything like that. Wondering if the CPU may work harder when memory resources a stretched thin?

Prior to this outage it appears the "Resource-Exhaustion-Detect" warning log entry appeared on average about 5 times per day starting August 10th or so.

125141-image.png


office-exchange-server-administration
image.png (305.2 KiB)
image.png (69.4 KiB)
image.png (68.7 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

YukiSun-MSFT avatar image
0 Votes"
YukiSun-MSFT answered YukiSun-MSFT edited

Hi @AdamTyler-3751,

I'm curious what would make the noderunner.exe processes go a bit nuts with CPU resources and now be totally quiet.

According to the following document, "Microsoft Exchange Host Controller Service starts four worker processes, and each is named NodeRunner.exe. NodeRunner.exe is part of the Exchange search component."
About the NodeRunner.exe process
So chances are that there were some search related tasks being processed when the outage occurred that consumed lots of memory.

Considering that things are getting better after allocating the additional RAM, you can just monitor it for some time and see if the current size of RAM can fit in your environment.


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.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @AdamTyler-3751,

Just checking to see if there are any updates. If you have any questions or need further help on this issue, please feel free to post back.


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.

0 Votes 0 ·