[ https://issues.apache.org/jira/browse/GEODE-2788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980003#comment-15980003 ]
ASF GitHub Bot commented on GEODE-2788: --------------------------------------- GitHub user masaki-yamakawa opened a pull request: https://github.com/apache/geode/pull/474 GEODE-2788: Add official Socket timeout parameter when connecting to servers/locators When connecting from the client to the servers/locators, if the servers/locators is not started, the connection can not be established and a Socket timeout occurs. This timeout value is 59 seconds by default. This timeout value is too long. This timeout value can be changed by specifying the unofficial parameter "gemfire.PoolImpl.HANDSHAKE_TIMEOUT" in java system property, but I corresponded so that it can be specified by official parameters. The official parameters are specified by the attribute of Pool.(default:59000 ms) For example, cache.xml like this: ```xml <pool name="MyPool" socket-connect-timeout="15000"> <locator host="localhost" port="10334" /> </pool> ``` API like this: ```java ClientCacheFactory().addPoolLocator("localhost", 10334).setPoolSocketConnecTimeout(15000); ``` or ```java PoolManager.createFactory().addServer("localhost", 40404).setSocketConnectTimeout(15000); ``` You can merge this pull request into a Git repository by running: $ git pull https://github.com/masaki-yamakawa/geode feature/GEODE-2788 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/geode/pull/474.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #474 ---- commit acd97c76a1e8f4690e8cd1050941c16e8f869502 Author: masaki.yamakawa <masaki.yamak...@ulsystems.co.jp> Date: 2017-04-22T15:44:08Z GEODE-2788: Add official Socket timeout parameter when connecting to servers/locators When connecting from the client to the servers/locators, if the servers/locators is not started, the connection can not be established and a Socket timeout occurs. This timeout value is 59 seconds by default. This timeout value is too long. This timeout value can be changed by specifying the unofficial parameter "gemfire.PoolImpl.HANDSHAKE_TIMEOUT" in java system property, but I corresponded so that it can be specified by official parameters. The official parameters are specified by the attribute of Pool.(default:59000 ms) For example, cache.xml like this: <pool name="MyPool" socket-connect-timeout="15000"> <locator host="localhost" port="10334" /> </pool> API like this: ClientCacheFactory().addPoolLocator("localhost", 10334).setPoolSocketConnecTimeout(15000); or PoolManager.createFactory().addServer("localhost", 40404).setSocketConnectTimeout(15000); ---- > Add official Socket timeout parameter when connecting to servers/locators > ------------------------------------------------------------------------- > > Key: GEODE-2788 > URL: https://issues.apache.org/jira/browse/GEODE-2788 > Project: Geode > Issue Type: Improvement > Components: client/server, docs > Reporter: Masaki Yamakawa > Priority: Minor > Labels: patch > > When connecting from the client to the servers/locators, if the > servers/locators is not started, the connection can not be established and a > Socket timeout occurs. > This timeout value is 59 seconds by default. This timeout value is too long. > This timeout value can be changed by specifying the unofficial parameter > "gemfire.PoolImpl.HANDSHAKE_TIMEOUT" in java system property, but I > corresponded so that it can be specified by official parameters. > Like the NativeClient, the official parameters should be specified by > "connect-timeout" in gemfire.properties. > Timeout values are determined in the following order of priority. > 1. java system property:gemfire.PoolImpl.HANDSHAKE_TIMEOUT > 2. java system property:gemfire.connect-timeout > 3. gemfire.properties:connect-timeout > 4. default:59000 milli seconds > As another idea, there is also an idea to make it possible to specify it as > an attribute of Pool. In that case NativeClient needs the same modification. -- This message was sent by Atlassian JIRA (v6.3.15#6346)