[GEODE-6677] Function with timeout, isHA==true and retries can lead to issues

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.10.0
• Labels: SmallFeature
• Assignee: Bill Burcham
• Reporter: Charlie Black
• Created: 18/Apr/19 22:07
• Updated: 26/Sep/19 18:04
• Resolved: 17/Jun/19 21:20

Description

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

 

Issue Links

• relates to: GEODE-6798 Refactoring client function execution logic
• links to: GitHub Pull Request #3593
• links to: GitHub Pull Request #3690
• links to: GitHub Pull Request #3715