You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Dick Cavender (Jira)" <ji...@apache.org> on 2019/09/26 18:05:07 UTC
[jira] [Closed] (GEODE-6677) Function with timeout, isHA==true and
retries can lead to issues
[ https://issues.apache.org/jira/browse/GEODE-6677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dick Cavender closed GEODE-6677.
--------------------------------
> Function with timeout, isHA==true and retries can lead to issues
> ----------------------------------------------------------------
>
> Key: GEODE-6677
> URL: https://issues.apache.org/jira/browse/GEODE-6677
> Project: Geode
> Issue Type: Bug
> Reporter: Charlie Black
> Assignee: Bill Burcham
> Priority: Major
> Labels: SmallFeature
> Fix For: 1.10.0
>
> Time Spent: 4h 50m
> Remaining Estimate: 0h
>
> A user can set `isHA() == true`, retries == -1, and `CLIENT_FUNCTION_TIMEOUT`.
> The timeout is currently implemented as per attempt. The default is 10000 ms.
> The default for retries is -1.
> With the default of -1 Geode will continually attempt to call the function and ignore the expected behavior.
>
> The expected behavior with respect to the default of -1 that means each server will be retried once and the system should throw an exception.
> From query the exception that is thrown is for system with 2 servers when the query exceeds the time out and retry of -1:
> {{Exception in thread "main" org.apache.geode.cache.client.ServerConnectivityException: Pool unexpected socket timed out on client connection=Pooled Connection to voltron:64615: Connection[voltron:64615]@1279740095 attempt=2). Server unreachable: could not connect after 2 attempts}}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)