Mailing-List: contact dev-help@geode.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geode.apache.org
Date: Sun, 16 Apr 2017 23:29:41 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: dev@geode.apache.org
Message-ID: <JIRA.13064301.1492382701000.293084.1492385381707@Atlassian.JIRA>
In-Reply-To: <JIRA.13064301.1492382701000@Atlassian.JIRA>
References: <JIRA.13064301.1492382701000@Atlassian.JIRA> <JIRA.13064301.1492382701107@jira-lw-us.apache.org>
Subject: [jira] [Commented] (GEODE-2788) Add official Socket timeout
 parameter when connecting to servers/locators
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Sun, 16 Apr 2017 23:29:49 -0000


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

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 se=
rvers/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 defaul=
t.
    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.
   =20
    Timeout values are determined in the following order of priority.
   =20
    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
   =20
    As another idea, there is also an idea to make it possible to specify i=
t as an attribute of Pool. In that case NativeClient needs the same modific=
ation.

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
   =20
----
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/locator=
s
   =20
    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.
   =20
    Timeout values =C3=A2=C2=80=C2=8B=C3=A2=C2=80=C2=8Bare determined and d=
etermined in the following
    order of priority.
   =20
    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/l=
ocators 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 lo=
ng. This timeout value can be changed by specifying the unofficial paramete=
r "gemfire.PoolImpl.HANDSHAKE_TIMEOUT" in java system property, but I corre=
sponded so that it can be specified by official parameters.
> Like the NativeClient, the official parameters should be specified by "co=
nnect-timeout" in gemfire.properties.
> Timeout values =E2=80=8B=E2=80=8Bare 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 modificat=
ion.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)