[ 
https://issues.apache.org/jira/browse/GEODE-8958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17288543#comment-17288543
 ] 

ASF GitHub Bot commented on GEODE-8958:
---------------------------------------

mhansonp commented on a change in pull request #6042:
URL: https://github.com/apache/geode/pull/6042#discussion_r580467363



##########
File path: 
geode-core/src/main/java/org/apache/geode/internal/cache/TombstoneService.java
##########
@@ -749,7 +751,8 @@ protected boolean hasExpired(long 
msTillHeadTombstoneExpires) {
         testHook_forceExpirationCount--;
         return true;
       }
-      return msTillHeadTombstoneExpires <= 0;
+      // In case
+      return msTillHeadTombstoneExpires <= 0 || msTillHeadTombstoneExpires > 
EXPIRY_TIME;

Review comment:
       That is the problem we are seeing. The customer is having timestamps far 
into the future. That is why we are putting this change in... So once we 
subtract now from oldest.getVersionTimeStamp() the number is far greater than 
EXPIRY_TIME. This is intended to catch that condition...




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Tombstone expiration: in the event that a version timestamp is too far in the 
> future, expire the tombstone
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-8958
>                 URL: https://issues.apache.org/jira/browse/GEODE-8958
>             Project: Geode
>          Issue Type: Bug
>          Components: core
>            Reporter: Mark Hanson
>            Assignee: Mark Hanson
>            Priority: Major
>              Labels: pull-request-available
>
> We are seeing a bug where for some reason, the version timestamp on the 
> tombstone is too far into the future to be realistic.
>  
> In such a case, we are going to expire the tombstone as soon as we see it.
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to