[
https://issues.apache.org/jira/browse/GEODE-10047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17492908#comment-17492908
]
ASF subversion and git services commented on GEODE-10047:
---------------------------------------------------------
Commit cd0b52e02bb4aeef7b35a2c5015cb7333481232e in geode's branch
refs/heads/develop from Donal Evans
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=cd0b52e ]
GEODE-10047: Fix expiration interval log (#7359)
- Change naming of passive expiration to active expiration throughout
the geode-for-redis module so as to be consistent with Redis' language
- Replace hard-coded expiration interval of 1 second with a reference to
the configured expiration interval in log message in
PassiveExpirationManager (now named ActiveExpirationManager)
Authored-by: Donal Evans <doev...@vmware.com>
> Warning message in geode-for-redis PassiveExpirationManager is inaccurate
> -------------------------------------------------------------------------
>
> Key: GEODE-10047
> URL: https://issues.apache.org/jira/browse/GEODE-10047
> Project: Geode
> Issue Type: Bug
> Components: logging, redis
> Affects Versions: 1.15.0, 1.16.0
> Reporter: Donal Evans
> Assignee: Donal Evans
> Priority: Major
> Labels: blocks-1.15.0, pull-request-available
>
> If an exception is encountered during the {{doDataExpiration()}} method in
> {{{}PassiveExpirationManager{}}}, the following message is logged:
> {code:java}
> logger.warn("Passive expiration failed. Will try again in 1 second.",
> ex);{code}
> However, the passive expiration interval in geode-for-redis defaults to 180
> seconds and can be configured by the user to other values. The log message
> should reflect the configured value for passive expiration interval.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
