[
https://issues.apache.org/jira/browse/GEODE-8958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17310902#comment-17310902
]
ASF subversion and git services commented on GEODE-8958:
--------------------------------------------------------
Commit a125d370cc737e87514ce97226b065362cb33a0b in geode's branch
refs/heads/master from mhansonp
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a125d37 ]
GEODE-8958: When tombstone timestamps get corrupted. (#6042)
- The system would wait, now it does expires it and moves on.
(cherry picked from commit 465ff56ccc7430ee7676bc8e8ae354e35fed3b3e)
> 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: blocks-1.14.0, pull-request-available
> Fix For: 1.12.2, 1.13.2, 1.14.0, 1.15.0
>
>
> 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)
