[jira] [Created] (GEODE-9148) expiration may be rescheduled when it is not needed

["Darrel Schneider (Jira)" <ji...@apache.org>]

Darrel Schneider created GEODE-9148:
---------------------------------------

             Summary: expiration may be rescheduled when it is not needed
                 Key: GEODE-9148
                 URL: https://issues.apache.org/jira/browse/GEODE-9148
             Project: Geode
          Issue Type: Improvement
          Components: expiration
            Reporter: Darrel Schneider


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. 



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