CODEWITHSUNDEEP
asp.netazureazure-caching
jmw
jmw

Reputation: 2864

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.

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?

Any ides or can somebody point me to any good resources describing cases like these?

Upvotes: 0

Views: 176

Answers (1)

astaykov
astaykov

Reputation: 30903

For use with SessionState you have to configure the caching role with "High Availability". 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.

Upvotes: 1

Related Questions