0

I am working on Azure solution (Azure SDK 2.1) with one web role (2 instances) and one worker role (2 instances). Both are using co-located (in-role) caching. The problem is that cache service on the worker role instances starting way too long - for several minutes every call to cache returns only DataCacheException-s saying that cache is temporary unavailable etc.

From your experience, is this normal? I think that cache service should be part of the "provisioned" environment, and should be already ready when Run method is called.

Is there anything I can do to handle this? Maybe some "event" to know when cache is ready? A way to say azure fabric to run my worker code only when cache is ready, etc. ?

4

1 回答 1

0

我们遇到了同样的问题,大多数人建议在您的 OnRun 事件中睡 2-3 分钟作为解决方法。

我很确定 Microsoft Azure 积压中有一个项目,除了等待使用缓存直到它准备好之外,他们并没有真正的解决方法。

我知道这不是最优雅的解决方案,但在我与微软不同人的谈话中,这暂时是他们的建议。

于 2013-09-16T18:23:50.600 回答