You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by anilkumar gingade <ag...@pivotal.io> on 2017/02/16 01:34:55 UTC
Re: Review Request 56729: GEODE-2490: Avoid processing tombstone GC
message in-line.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/56729/
-----------------------------------------------------------
(Updated Feb. 16, 2017, 1:34 a.m.)
Review request for geode, Darrel Schneider and Eric Shu.
Summary (updated)
-----------------
GEODE-2490: Avoid processing tombstone GC message in-line.
Repository: geode
Description
-------
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.
Currently the tombstone message sent for replicas are getting processed in-line instead of handing it to thread pool. Based on the number of nodes in the cluster, this may take long time to process, impacting other cache operation that required to be processed in-line.
The change provided here enables tombstone messages to be not processed in-line instead processed in separate thread.
Diffs
-----
geode-core/src/main/java/org/apache/geode/internal/cache/DistributedTombstoneOperation.java 0765e16
geode-core/src/test/java/org/apache/geode/cache30/ClientServerCCEDUnitTest.java 9780563
Diff: https://reviews.apache.org/r/56729/diff/
Testing
-------
New test added.
precheckin.
Thanks,
anilkumar gingade