[
https://issues.apache.org/jira/browse/GEODE-8958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17294889#comment-17294889
]
ASF subversion and git services commented on GEODE-8958:
--------------------------------------------------------
Commit 3ffc6a6aaaf9a0ed9245d7069dd6cfdc68d5c936 in geode's branch
refs/heads/support/1.12 from Mark Hanson
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=3ffc6a6 ]
GEODE-8958: When timestamps get corrupted.
Fixing an import issue.
(cherry picked from commit 3e1e3b0a7114801c3ce832a6e164e35ff9edd7d7)
> 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
>
> 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)
