[GEODE-9148] expiration may be rescheduled when it is not needed

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.15.0
• Component/s: expiration
• Labels: GeodeOperationAPI pull-request-available
• Assignee: Darrel Schneider
• Reporter: Darrel Schneider
• Created: 13/Apr/21 22:28
• Updated: 22/Jun/22 20:46
• Resolved: 15/Dec/21 00:02

Description

Geode expiration is configured with timeouts whose units are seconds. But the internal implementation uses milliseconds. I noticed recently that for whatever reason, the Timer was firing scheduled events a few milliseconds early. This caused the expiration code to reschedule it for just a few milliseconds and then do all the expiration checking again. It has also been noticed that last-access-time expiration may find a timestamp on another member that is just a few milliseconds away from expiration. Once again this causes a reschedule.

It seems like if the millisecond time is within 500 millis of expiring then we could go ahead and expire without rescheduling. 

Issue Links

• links to: GitHub Pull Request #6514