需要同时启动具有持久数据的所有gemfire成员

问题描述 投票:0回答:1

[之前我在开发环境中的Gemfire集群上调用GFSH shutdown命令时,我仍然需要等待其余的Gemfire缓存服务器成员重新启动。为什么?

我以为,当我调用GFSH关机命令时,所有成员都将运行,所有在线数据存储区将在关闭前进行同步,因此所有文件都将保存最新的数据副本。因此,所有缓存服务器成员将具有最新记录。

软件配置

  1. 4高速缓存服务器
  2. 2定位器
  3. Gemfire 9.8.4
  4. 持久性复制区域

例如,如果我在Gemfire群集上调用了GFSH关闭命令,然后在所有计算机上执行关闭操作。然后,我启动2个定位器和3个缓存服务器。它会等待剩余的缓存服务器吗?

添加

在缓存服务器日志中

[info ...19:27:02.327...... <main> tid=0x1] Created oplog#9 drf for disk store pdxMetaDataStore
[info ...19:27:02.327...... <main> tid=0x1] Created oplog#9 crf for disk store pdxMetaDataStore
[info ...19:27:02.327...... <main> tid=0x1] Deleted oplog#8 crf for disk store pdxMetaDataStore
[info ...19:27:02.327...... <main> tid=0x1] Deleted oplog#8 drf for disk store pdxMetaDataStore
[info ...19:27:02.329...... <main> tid=0x1] recovery region initialization took 17 ms
[info ...19:27:02.355...... <main> tid=0x1] Initializing region PdxTypes
[info ...19:31:31.509...... <unicast-receiver,gf-1> receive new view: View[148.88.88.100....
.....
[info ...19:31:31.514...... Admitting member...
[info ...19:31:31.514...... Region PdxTypes requesting initial image from 148.88.88.100...
[info ...19:31:31.514...... PdxTypes is done getting image from 148.88.88.100.

仅当启动另一个缓存服务器时,初始化完成的区域PdxTypes。

server-cache.xml

<disk-store name="pdxMetaDataStore" compaction-threshold="40" auto-compact="false" allow-force-compaction="true" max-oplog-size="75" queue-size="10000" time-interval="15" write-buffer-size="65535">
<disk-dirs>
  <disk-dir dir-size="3000">/gemfire/store</disk-dir>
</disk-dirs>
</disk-store>
<pdx read-serialized="true" disk-store-name="pdxMetaDataStore" persistent="true/>

GFSH

Disk Store ID                        |  Host          | Directory
--------------------------------------------------------------------
66asdf-asdf-asdf-asdf-asdfafadfasfC  | 148.88.88.100  | /gemfire/store
gemfire
1个回答
0
投票

我刚刚看到了更新的描述和日志摘录,只要成员离开或加入分布式系统(内部同步机制),这些消息在GemFire集群中都是常见的,它们不暗示服务器正在等待其他服务器启动并完成初始化,在这种情况下,您会看到类似以下内容:

Region /MyRegion has potentially stale data.
It is waiting for another member to recover the latest data.
My persistent id:

  DiskStore ID: 6893751ee74d4fbd-b4780d844e6d5ce7
  Name: server1
  Location: /192.0.2.0:/home/dsmith/server1/.

Members with potentially new data:
[
  DiskStore ID: 160d415538c44ab0-9f7d97bae0a2f8de
  Name: server2
  Location: /192.0.2.0:/home/dsmith/server2/.
]
Use the "gfsh show missing-disk-stores" command to see all disk stores
that are being waited on by other members.

您可以在this帖子中查看有关“获取初始图像序列”序列的更多信息。

干杯。

© www.soinside.com 2019 - 2024. All rights reserved.