关注速度 [英] Concern of Velocity

问题描述

对于我来说，速度超过所有模型对我来说都不是很好，因为以下的回复

With the over all model of Velocity doesn't looks great to me because of the following resons

- 想象一下我是3个实例，其中一个是Lead Host，其余的是Cache主机，虽然我有3个实例我的整个设置依赖于Lead Host   -
这是单点故障（如果我的主机主机出现故障，那么我的整个设置都已消失）所以我运行群集是没有意义的。

- Imagine I've 3 instances out of which one is Lead Host and rest of them are Cache host though I've 3 instance my entire setup is still depending on Lead Host - this is single point of failure(If my Lead Host fails then my entire setup is gone) so it doesnt make sense for me to run cluster.

 

我的理解有什么不妥。

 

< strong style ="font-weight：bold; font-style：inherit; font-family：inheri t; outline-width：0px;概括式family：宋体;轮廓色：初始;填充：0像素;保证金：0像素; border：0px initial initial">

推荐答案

可能还有其他想法，但我认为你可以通过两种可能的方式最大限度地减少对单点故障的担忧：

There may be other thoughts on this, but I think you can minimize this concern about the single-point-of-failure in two possible ways:

1.你可以制作所有三个缓存3节点集群中的主机引导主机。这意味着只有当2个缓存主机发生故障时，集群才会关闭（如果每个容量计划需要全部三个，那么它可能会耗尽内存，只有一个主机上升
无论如何）。请参阅：设置群集管理角色和主机主机名称（Windows Server AppFabric缓存）。

1. You can make all three cache hosts in a 3-node cluster lead hosts. This means that the cluster will only go down if 2 of the cache hosts fail (if you need all three per capacity planning, then it probably would run out of memory with only one host up anyway). See: Set the Cluster Management Role and Lead Host Designations (Windows Server AppFabric Caching).

2.如果您将SQL Server用于配置存储，则缓存集群可以仅运行一个缓存主机（假设它不会被负载淹没）。

2. If you use SQL Server for the configuration store, then the cache cluster could run with only one cache host running (assuming it is not overwhelmed by the load).

这些是否使AppFabric缓存解决方案更加可行？

Do these make the AppFabric Caching solution more viable to you?

Jason Roth

Jason Roth

这篇关于关注速度的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！