Quote Originally Posted by WWGT View Post
If I've read the documpentation correctly, this means while the pool is auto restarting the webapp will still be available?
That is true, instead of ending all processes and then starting a whole new bunch of processes it now stops one, starts one, stops one and starts one until it has refreshed all processes. While this is done it does continue to process requests.

Quote Originally Posted by WWGT View Post
If so, did you consider that the new processes in the pool shouldn't be able to process requests until all the processes are restarted (because of potential differences)?
No, it doesn't consider that. During this restart it there will be a mix of old and new processes handling requests for a few seconds (depending on the pool size and how long it takes to start & stop processes). If we would start a whole new pool and then switch over there is the situation where you temporary have more processes than configured which could potentially cause issues because too many resources are used (or licensing issues).

Quote Originally Posted by WWGT View Post
A different question that's a bit off topic, in 19.0 when we manually restart a webapp there's a great chance you can't access any webapp on that server untill that webapp is done restarting. Has this been addressed in 19.1 and/or 2020?
The change above only applies to the automatic reload. A manual restart (via the administrator) still takes the application down (stops all processes, and then starts a whole new set) temporary. I do think that we improved the startup so that it does start to process requests as soon as the first process is ready instead of waiting for the entire pool to be filled.