主机未运行；请求将排队，但要等到主机启动后才能执行 [英] Host is not running; requests will be queued but not execute until the host is started

问题描述

通常，当我重新发布具有一些小的更改的Web作业并尝试重新运行Web作业功能时，SCM在Web门户中向我显示以下警告，而我无法执行该功能

Often when I republish a webjob with some minor changed and try to Rerun a Webjob function SCM shows me the following warning in the web portal, and I cannot execute the function

主机未运行；请求将排队，但直到执行 主机已启动.

Host is not running; requests will be queued but not execute until the host is started.

在这种情况下，主机始终处于运行状态，并且作业设置为单例，多台主机应该没有问题.

The host is always running in this case, and the job is setup as singleton, there should not be a problem with multiple hosts.

推荐答案

WebJobs仪表板将显示此消息，直到它从主机接收到更新的心跳"消息，表明该主机正在运行. JobHost将心跳消息写入Blob存储(位于/heartbeats 下的 azure-webjobs-hosts 容器中).仪表板会轮询心跳信号以获取特定的主机ID，并在检测到主机尚未开始运行时显示此消息.从主机启动到仪表板看到Blob更新之间，可能会有 minimum 延迟.

The WebJobs Dashboard shows this message until it receives an updated "heartbeat" message from the host indicating that the host is running. The JobHost writes the heartbeat message into blob storage (in the azure-webjobs-hosts container under path /heartbeats). The Dashboard polls the heartbeat blob for a particular host ID and shows this message when it detects the host hasn't started running yet. There might be a minimal delay between when the host starts up and when the Dashboard sees the blob update.

这篇关于主机未运行；请求将排队，但要等到主机启动后才能执行的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！