[英]Azure co-located cache session state (instance failure/updates)
How does azure co-located cache when used for session state through the DistributedCacheSessionStateStoreProvider handle scenarios where the instances is updated (rolling/incremental) or if there is a failure on one of the instances. 当通过DistributedCacheSessionStateStoreProvider用于会话状态时,天蓝色的同位缓存将如何处理更新实例(滚动/增量)或实例之一发生故障的情况。
Is all co-located cache data replicated to all instances or is some data lost on failures? 是否将所有位于同一地点的缓存数据复制到所有实例,还是某些数据因故障而丢失?
If for example request #1 is handle by instance 0 and then instance 0 crashes/updates can request #2 that is handled by instance 1 continue to access the same Session state data from the previous request? 例如,如果请求#1由实例0处理,然后实例0崩溃/更新,实例1处理的请求#2是否可以继续访问先前请求中的相同会话状态数据?
Any ides or can somebody point me to any good resources describing cases like these? 是否有任何想法或人可以向我指出描述此类情况的任何良好资源?
For use with SessionState you have to configure the caching role with "High Availability". 要与SessionState一起使用,必须将缓存角色配置为 “高可用性”。 This will make all cache entries distributed among all instances of the role. 这将使所有缓存条目在角色的所有实例之间分配。 So a cache item will not be lost upon instance updates / recycles. 因此,在实例更新/回收时缓存项不会丢失。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.