问题描述
我正在使用Azure托管云服务，我最近修改为可跨多个实例扩展，包括会话缓存工作者角色。我的问题是，为什么我会看到极端负载（90％以上）在一个实例，但不是在其他实例（15-20％在所有其他实例）？我应该担心吗？
I'm utilizing Azure for hosting a cloud service, which I recently modified to be scalable across multiple instances, including a session caching worker role. My question is, why would I be seeing extreme load (upwards of 90%) on one instance, but not on other instances (15-20% across all other instances)? Should I be worried?
在设置负载平衡之前，当我的单个实例达到95％的负载时，它会缓慢爬行 - 变得不可用。有没有办法确保我没有任何用户体验到这种情况，因为他们以某种方式循环到重载的实例？
Before I set up load balancing and when my single instance hit upwards of 95% load, it would slow to a crawl --- becoming unusable. Is there any way to ensure that I don't have any users experiencing this because they're somehow round-robin'd onto the overloaded instance?
推荐答案
我们发现我们有一个类似的情况，当一个负载平衡的实例故障转移;我们看到的是所有的负载转移，但不会再平衡。我们发现关闭保持活动几分钟，让负载再次传播，之后我们可以重新启用它。
We found we had a similar type of situation when one load-balanced instance failed over; what we were seeing is that all the load transferred, but wouldn't balance out again. We found that turning off keep-alive for a couple of minutes let the load spread again, after which we could turn it back on.
这篇关于极不平衡的云服务负载平衡与Azure的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！