为什么'Get-CacheClusterHealth'并不总是返回所有节点？ [英] Why does 'Get-CacheClusterHealth' not always return all nodes?
问题描述
我有一个双节点集群。在Windows Server 2008 R2 Standard上运行AppFabric的发行版。我只使用缓存服务。
I have a two node cluster. Running the release version of AppFabric on Windows Server 2008 R2 Standard. I am using only the cache service.
请在我的主节点上查看以下PowerShell会话：
Please take a look at the following PowerShell session on my primary node:
PS C：\ Windows \ system32> Get-CacheClusterHealth
群集健康统计数据
==================== =====
$
HostName = NotCache01
------------------ -------
NamedCache =默认
健康              = 50.00
UnderReconfiguration = 0.00
NotPrimary           = 0.00
NoWriteQuorum        = 0.00
节流            = 0.00
$
未分配的命名缓存分数
------------ ---------------------
NamedCache =默认
未分配的分数 = $ 50.00
$
PS C：\ Windows \ SYSTEM32> Get-CacheClusterHealth
群集健康统计数据
==================== =====
$
HostName = NotCache01
------------------ -------
NamedCache =默认
健康              = 50.00
UnderReconfiguration = 0.00
NotPrimary           = 0.00
NoWriteQuorum        = 0.00
节流            = 0.00
$
未分配的命名缓存分数
------------ ---------------------
NamedCache =默认
未分配的分数 = $ 50.00
$
PS C：\ Windows \ SYSTEM32> get-cachehost
HostName：CachePort 服务名称 服务状态版本信息
-------------------- ------------            -------------- ------------
$
NotCache01：22233    AppFabricCachingService UP 1 [1,1] [1,1]
NotCache02：22233 AppFabricCachingService UP 1 [1,1] [1,1]
PS C：\ Windows \ system32> Get-CacheClusterHealth
群集健康统计数据
==================== =====
$
HostName = NotCache01
------------------ -------
NamedCache =默认
健康              = 50.00
UnderReconfiguration = 0.00
NotPrimary           = 0.00
NoWriteQuorum        = 0.00
节流            = 0.00
$
HostName = NotCache02
------------- ------------
NamedCache =默认
健康              = 50.00
UnderReconfiguration = 0.00
NotPrimary           = 0.00
NoWriteQuorum        = 0.00
节流            = 0.00
$
未分配的命名缓存分数
------------ ---------------------
PS C：\ Windows \system32>
PS C:\Windows\system32> Get-CacheClusterHealth
Cluster health statistics
=========================
HostName = NotCache01
-------------------------
NamedCache = default
Healthy = 50.00
UnderReconfiguration = 0.00
NotPrimary = 0.00
NoWriteQuorum = 0.00
Throttled = 0.00
Unallocated named cache fractions
---------------------------------
NamedCache = default
Unallocated fraction = 50.00
PS C:\Windows\system32> Get-CacheClusterHealth
Cluster health statistics
=========================
HostName = NotCache01
-------------------------
NamedCache = default
Healthy = 50.00
UnderReconfiguration = 0.00
NotPrimary = 0.00
NoWriteQuorum = 0.00
Throttled = 0.00
Unallocated named cache fractions
---------------------------------
NamedCache = default
Unallocated fraction = 50.00
PS C:\Windows\system32> get-cachehost
HostName : CachePort Service Name Service Status Version Info
-------------------- ------------ -------------- ------------
NotCache01:22233 AppFabricCachingService UP 1 [1,1][1,1]
NotCache02:22233 AppFabricCachingService UP 1 [1,1][1,1]
PS C:\Windows\system32> Get-CacheClusterHealth
Cluster health statistics
=========================
HostName = NotCache01
-------------------------
NamedCache = default
Healthy = 50.00
UnderReconfiguration = 0.00
NotPrimary = 0.00
NoWriteQuorum = 0.00
Throttled = 0.00
HostName = NotCache02
-------------------------
NamedCache = default
Healthy = 50.00
UnderReconfiguration = 0.00
NotPrimary = 0.00
NoWriteQuorum = 0.00
Throttled = 0.00
Unallocated named cache fractions
---------------------------------
PS C:\Windows\system32>
这些命令在快速继承，那么，为什么辅助节点在我尝试运行Get-CacheClusterHealth的前两次没有返回数据？
These commands were run in quick succession, so, why does the secondary node not return data the first two times I attempt to run Get-CacheClusterHealth?
很多谢谢，
Jamie
推荐答案
"未分配的命名缓存分数"指示要分配给某个节点的待处理缓存的百分比，未显示任何未完成贡献的节点。未分配的分数为非零 表示所有
群集节点都不健康，并且客户端请求可能会在此期间重试稍后/超时错误。 由于第二个节点已准备好服务器请求，因此显示在列表中。
The "unallocated named cache fractions" indicate the percentage of cache that is pending to be assigned to some node, the nodes which are not contributing at all are not shown. Unallocated fractions being non-zero indicates all cluster nodes are not healthy and client requests may get retry later/timeout errors in that period. As the second node is ready to server requests, it is shown in the list.
在群集启动时或当一个或多个节点状况不佳时，未分配的分数可能非零，例如最近一个节点出现故障，该节点所服务的缓存的比例需要在剩余的节点上共享。将这些分数的
分配到其他节点可能需要几秒钟。
The unallocated fractions can be non-zero at cluster startup or when one or more nodes are not in good shape, e.g. a node recently went down and the fraction of the caches being served by that node needs to be shared across the remaining. The assignment of these fractions to other nodes can take a few seconds.
这篇关于为什么'Get-CacheClusterHealth'并不总是返回所有节点？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
