[
https://issues.apache.org/jira/browse/GEODE-2788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005543#comment-16005543
]
ASF GitHub Bot commented on GEODE-2788:
---------------------------------------
Github user metatype commented on a diff in the pull request:
https://github.com/apache/geode/pull/474#discussion_r115865619
--- Diff:
geode-core/src/main/resources/META-INF/schemas/geode.apache.org/schema/cache/cache-1.0.xsd
---
@@ -1191,6 +1191,7 @@ As of 6.5 disk-dirs is deprecated on
region-attributes. Use disk-store-name inst
</xsd:complexType>
</xsd:element>
</xsd:choice>
+ <xsd:attribute name="socket-connect-timeout" type="xsd:string"
use="optional" />
--- End diff --
BTW, if we change the XSD it needs to get posted on geode.apache.org via
the asf-site branch of geode-site.
> 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)
