IIS应用程序池回收和“关闭时间限制"将在步骤2中给出.重叠中的作用 [英] IIS application pool recycling and "shutdown time limit" role in overlapping

问题描述

发生回收时，我想将所有新请求移至新的w3wp(这是自动完成的)，并在空闲时(无论花费多长时间)使之前的w3wp退出.

When recycling happens, I want to move all new request to new w3wp (this is done automatically) and leave the previous w3wp to exit when it gets idle (whatever time it takes).

有一个用于应用程序池的shutdown time limit配置(我使用IIS 7.0)，它的值不为0.完成并处于空闲状态时，如何让以前的w3wp关闭.

There's a shutdown time limit config for application pools (I use IIS 7.0) which doesn't take 0 as a value. How can I let the previous w3wp to shutdown when it is done and idle.

推荐答案

关闭时间限制提示使旧的工作进程运行直至所指示的秒数.如果所有请求均在该时间之前完成，则它将更早关闭.

The shutdown time limit hint leaves the old worker process running for up to the number of seconds indicated. If all requests are completed prior to that time, then it will shut down earlier.

发生回收时，一个新的工作进程启动，并立即开始接受新的请求. old 工作进程继续处理旧的进行中的请求，直到完成或直到达到关闭时间限制为止.顺便说一句，最大关闭时间限制秒似乎是4294967，比50天少了1秒. OMG，我希望没有人等那么长时间才能完成请求！

When recycling happens, a new worker process spins up and immediately begins taking new requests. The old worker process continues working on old in-flight requests until completed, or until the shutdown timelimit is reached. By the way, the maximum shutdown timelimit seconds appears to be 4294967 which is one second shy of 50 days. OMG I hope no one is waiting that long for a request to complete!

从理论上讲，新的辅助进程可能实际上无法启动，尤其是在没有足够的可用内存的情况下.

Parenthetically, it is possible for a new worker process to NOT actually be able to start, especially if there is not enough free memory.

这篇关于IIS应用程序池回收和“关闭时间限制"将在步骤2中给出.重叠中的作用的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！