VMware环境中的AppFabric缓存

问题描述

在虚拟环境中工作，定期移动VM以获得最佳资源，这意味着缓存服务器在移动过程中暂时不可用。这可能需要15秒，平均到一分钟。我猜这个不可用的
导致时间敏感的集群运行状况算法出现问题。

查看DistributedCacheService.exe.config，有一个名为fabric\section的配置元素" param" \ClusterStableNodeUpInterval，其值由安装向导设置为10. 

MSDN表示通常不应触及此值，但此值以秒表示，毫秒或其他时间单位？

我们应该如何期望AppFabric在虚拟环境中工作，具有动态资源控制？

非常感谢，

解决方案

Hi,

Working in a virtual environment, where VMs are periodically moved for optimal resources, means that cache servers are temporarily unavailable whilst the move takes place. This can take 15 secs on average, to a minute. I guess that this unavailability could cause problems in time-sensitive cluster health algorithms.

Looking at the DistributedCacheService.exe.config, there is a configuration element called fabric\section "param"\ClusterStableNodeUpInterval, whose value was set to 10 by the installation wizard. 

MSDN says that this value should not normally be touched, but is this value expressed in seconds, milliseconds or another time unit?

How should we expect AppFabric to work in a virtual environment, with dynamic resource control?

Many thanks,

解决方案

这篇关于VMware环境中的AppFabric缓存的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！