Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>We use Azure co-located caching (not in preview anymore) as our session backer and have fairly regular outages. About once a month.</p> <p>We tried using the Enterprise library <a href="http://msdn.microsoft.com/en-us/library/hh680905%28v=pandp.50%29.aspx" rel="nofollow">Transient Fault Handling</a> but our instances still hang when caching experiences problems. I think that the transient fault code would work for data caching, but for session backing there is some activity closer to the metal that we can't seem to code against.</p> <p>The error codes have become more informative over the last year and go something like...</p> <blockquote> <p>ErrorCode:SubStatus:The request timed out.. Additional Information : The client was trying to communicate with the server: net.tcp://10.xx.xxx.xx:xxxxx/.</p> </blockquote> <p>Our best guess so far from experimenting and MS support is that each, or at least one co-located cache role/instance needs to know about all the other instance's IPs, since Azure can destroy and re-up instances whenever they want, this sometimes fails to update the dependent instances. This is secret sauce for Azure, but it is not a secret when our site goes down. I'm looking for any more information on this and to see how others are working around this issue.</p> <p><strong>One possible work-around.</strong> One of our talented platform administrators found that resetting IIS on the instances and scaling up two more instances seem to help the problem. This makes sense to me because it gives caching another chance to gather all the required info about the other instances. This is NOT CONFIRMED to solve the problem but if we repeat this during the next outage it could be a valid work around.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload