[ https://issues.apache.org/jira/browse/GEODE-2788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16018818#comment-16018818 ]
ASF GitHub Bot commented on GEODE-2788: --------------------------------------- GitHub user masaki-yamakawa opened a pull request: https://github.com/apache/geode-site/pull/4 GEODE-2788: Add official Socket timeout parameter when connecting to servers/locators Add socket-connect-timeout to the Pool attribute. This attribute is optional. Related changes: https://github.com/apache/geode/pull/474 You can merge this pull request into a Git repository by running: $ git pull https://github.com/masaki-yamakawa/geode-site feature/GEODE-2788 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/geode-site/pull/4.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 #4 ---- commit f6031b37ba960531162155c63fb903e21a0ca6e8 Author: masaki.yamakawa <masaki.yamak...@ulsystems.co.jp> Date: 2017-05-21T13:06:57Z GEODE-2788: Add official Socket timeout parameter when connecting to servers/locators Add socket-connect-timeout to the Pool attribute. This attribute is optional. ---- > 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)