we have a small nodejs site hosted on app service on linux serving static content (+ some middleware actions) from an azure storage blob preventing whole site to recycle if new content are pushed onto the blob.
(我们app service on linux上的app service on linux托管了一个小型的nodejs网站，该app service on linux从azure存储blob中提供静态内容（以及一些中间件操作），以防止将新内容推送到blob时整个网站进行回收。)
For some reasons, probably network ones, azure storage mount is sometimes detected as faulty and when connection is restaured, it triggers the whole app service to recycle blocking serving any contents meanwhile and prevents more friendly waiting message.
(由于某些原因（可能是网络原因），有时会检测到azure存储安装错误，并且在恢复连接后，它会触发整个app service循环回收阻止同时提供任何内容，并阻止更友好的等待消息。)
2019-11-30 15:33:16.726 ERROR - Azure storage volume kiteblob for site kite faulted.
2019-11-30 15:34:01.615 INFO - Azure storage volume kiteblob for site kite became healthy. Recycling site.
any way to prevent this behavior without hardening the whole service ?
(在不强化整个服务的情况下有什么方法可以防止这种行为？)
it's a small website serving few number of pages/users for internal purpose. (这是一个小型网站，仅出于内部目的提供少量页面/用户。)
ask by camous translate from so 与恶龙缠斗过久,自身亦成为恶龙；凝视深渊过久,深渊将回以凝视…
