[
https://issues.apache.org/jira/browse/GEODE-9654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17431350#comment-17431350
]
ASF subversion and git services commented on GEODE-9654:
--------------------------------------------------------
Commit d3104cceb4714d49d5540691a3c628cda8b5efb5 in geode's branch
refs/heads/develop from Hale Bales
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d3104cc ]
GEODE-9654: add system properties for timeouts (#6961)
Adds system properties for geode-for-redis-write-timeout-seconds and
geode-for-redis-interval-seconds
- If they are set to non-integer, negative, or zero, the default values will
quietly be used.
- add tests for helper for setting timeouts
- renames
- add support for both geode. and gemfire. prefixes for timeout properties
> Add system property for configuring redis timeouts
> --------------------------------------------------
>
> Key: GEODE-9654
> URL: https://issues.apache.org/jira/browse/GEODE-9654
> Project: Geode
> Issue Type: Improvement
> Components: redis
> Reporter: Hale Bales
> Assignee: Hale Bales
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> We have a some hard coded timeouts in our redis module that may or may not
> work in our customer environments. We should probably make some these things
> configurable with system properties so support could help customers get pass
> issues if these timeouts don't work.
> In NettyRedisServer:
> - CONNECT_TIMEOUT_MILLIS
> - new WriteTimeoutHandler(10)
> PassiveExpirationManager.INTERVAL
> We shall sweep through the code and find other hardcoded constants and see if
> we want there to be a chance for support to configure them.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
