[
https://issues.apache.org/jira/browse/GEODE-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15879354#comment-15879354
]
ASF subversion and git services commented on GEODE-2489:
--------------------------------------------------------
Commit 257c21ece8ac54cf3ead2c41bfe8085b3219e3d5 in geode's branch
refs/heads/develop from [~agingade]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=257c21e ]
GEODE-2489: Avoid sending tombstone GC messages to peer nodes if there is no
client registration
When tombstones are removed, tombstone messages are sent to region replicas;
and in case of Partitioned Region (PR) messages are also sent to peer region
nodes for client events.
Currently tombstone messages meant for clients that have all the keys removed
are getting sent to peer PR nodes even though no clients are registered on
those peers.
> Tombstone message with keys are sent to peer partitioned region nodes even
> though no clinets are registered
> -----------------------------------------------------------------------------------------------------------
>
> Key: GEODE-2489
> URL: https://issues.apache.org/jira/browse/GEODE-2489
> Project: Geode
> Issue Type: Bug
> Components: regions
> Reporter: Anilkumar Gingade
>
> Tombstone:
> As part of consistency checking, when an entry is destroyed, the member
> temporarily retains the entry to detect possible conflicts with operations
> that have occurred. The retained entry is referred to as a tombstone.
> When tombstones are removed, tombstone messages are sent to region replicas;
> and in case of Partitioned Region (PR) messages are also sent to peer region
> nodes for client events.
> Currently tombstone messages meant for clients that have all the keys removed
> are getting sent to peer PR nodes even though no clients are registered on
> those peers.
> Based on the number tombstone keys processed (by default 100000) this could
> be large message sent to peer node which could impact the performance of the
> system/cluster.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
