Red Hat Summit 红帽全球峰会支持控制台（Console）开发人员开始试用联系人

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

25.4. Distributed Garbage Collection (STABLE)

In a JGroups cluster, all nodes must store all messages received for potential retransmission in case of a failure. However, if we store all messages forever, we will run out of memory. The distributed garbage collection service periodically purges messages that have been seen by all nodes, removing them from the memory in each node. The distributed garbage collection service is configured in the pbcast.STABLE sub-element under the JGroups config element. Here is an example configuration. 
<pbcast.STABLE stability_delay="1000"
    desired_avg_gossip="5000" 
    max_bytes="400000"/>
Copy to Clipboard Toggle word wrap
The configurable attributes in the pbcast.STABLE element are as follows.
  • desired_avg_gossip specifies intervals (in milliseconds) of garbage collection runs. Set this to 0 to disable interval-based garbage collection.
  • max_bytes specifies the maximum number of bytes received before the cluster triggers a garbage collection run. Set to 0 to disable garbage collection based on the bytes received.
  • stability_delay specifies the maximum time period (in milliseconds) of a random delay introduced before a node sends its STABILITY message at the end of a garbage collection run. The delay gives other nodes concurrently running a STABLE task a chance to send first. If used together with max_bytes, this attribute should be set to a small number.

Note

Set the max_bytes attribute when you have a high traffic cluster.
返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

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

让开源更具包容性

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

關於紅帽

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

Theme

© 2025 Red Hat