此内容没有您所选择的语言版本。

28.5. Merging (MERGE2)


When a network error occurs, the cluster might be partitioned into several different partitions. JGroups has a MERGE service that allows the coordinators in partitions to communicate with each other and form a single cluster back again. The merging service is configured in the MERGE2 sub-element under the JGroups Config element. Here is an example configuration.
<MERGE2 max_interval="10000"
    min_interval="2000"/>
Copy to Clipboard Toggle word wrap
The configurable attributes in the MERGE2 element are as follows.
  • max_interval specifies the maximum number of milliseconds to wait before sending a MERGE message.
  • min_interval specifies the minimum number of milliseconds to wait before sending a MERGE message.
JGroups chooses a random value between min_interval and max_interval to periodically send the MERGE message.

Note

The application state maintained by the application using a channel is not merged by JGroups during a merge. This must be done by the application.

Note

If MERGE2 is used in conjunction with TCPPING, the initial_hosts attribute must contain all the nodes that could potentially be merged back, in order for the merge process to work properly. Otherwise, the merge process may not detect all sub-groups, and may miss those comprised solely of unlisted members.
返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2025 Red Hat