geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-2788) Add official Socket timeout parameter when connecting to servers/locators
Date Sun, 16 Apr 2017 23:29:41 GMT

    [ https://issues.apache.org/jira/browse/GEODE-2788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15970551#comment-15970551
] 

ASF GitHub Bot commented on GEODE-2788:
---------------------------------------

GitHub user masaki-yamakawa opened a pull request:

    https://github.com/apache/geode/pull/458

    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 done by
    specifying the informal parameter "gemfire.PoolImpl.HANDSHAKE_TIMEOUT"
    in java the system property, but we corresponded so that it can be
    specified by official parameters.
    
    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.

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/458.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 #458
    
----
commit 261c6ee7c6e8af75d1c3c206214efc64e6e03fee
Author: masaki.yamakawa <masaki.yamakawa@ulsystems.co.jp>
Date:   2017-04-16T16:46:03Z

    dd 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 done by
    specifying the informal parameter "gemfire.PoolImpl.HANDSHAKE_TIMEOUT"
    in java the system property, but we corresponded so that it can be
    specified by official parameters.
    
    Timeout values ​​are determined and 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

----


> 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: core
>            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)

Mime
View raw message