All geek questions in one place

Does editing the Web.config file do overlapping processing or start + stop the application pool?

I have Overlapping Recycling configured for my ASP.NET MVC site.

As I understand it ( from this SO question ), if I recycle the application pool, it will start a new w3wp.exe process to load the load of the one that is being processed, and only when the new process is initialized and loaded will the old process be disconnected. And if I stop / start the application pool, it will destroy immediately, preventing the process from exiting gracefully or allowing the first to start the replacement process.

Question: when I edit the Web.config file, it will restart the associated IIS application pool. Will this lead to a good coincidence of the recirculation regime or to a violent cessation / onset of behavior?

I am trying to decide if I need to get the server out of the load-balanced farm and do a stop-stop on server traffic in order to edit the configuration settings.

+4
source share
2 answers

I decided to use science. I experimented with my server under a load testing tool, where I repeatedly edited and saved the Web.config file when requests were uploaded.

No queries were deleted when the changes were saved to the Web.config file.

, , .

, , Web.config . .

, , process id Web.config. IIS Overlapping Recycle IIS, w3wp.exe, . . , Overlapping Recycle.

process id , , , / AppDomain. , , :

a

Web.config . . configSource , . . ConfigSource Inherited .

TL;DR

Recycle, stop/start Web.config. AppDomain .

http://msdn.microsoft.com/en-us/library/ackhksh7.aspx

+5

( ) web.config " ". , "", , . . , WCF-Service, IIS7.5, IProcessHostPreloadClient, . , "", IIS, : , .

+1

Source: https://habr.com/ru/post/1569419/

More articles:


All Articles