You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/07/02 10:27:00 UTC
[jira] [Commented] (GEODE-2891) connect-timeout violation in C++
Native Client
[ https://issues.apache.org/jira/browse/GEODE-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071582#comment-16071582 ]
ASF GitHub Bot commented on GEODE-2891:
---------------------------------------
GitHub user gregt5259 opened a pull request:
https://github.com/apache/geode-native/pull/105
GEODE-2891 connect-timeout violation in C++ Native Client
THe fix enables to interpret the time measure unit in handshake as milliseconds rather than seconds.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gregt5259/geode-native develop
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/geode-native/pull/105.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 #105
----
commit d4c84019fc225a9a83f8a23f127ccc6fcddf4146
Author: gregt5259 <gr...@amdocs.com>
Date: 2017-07-02T07:27:50Z
Merge remote-tracking branch 'refs/remotes/apache/develop' into develop
commit c5743fea51b390338f9cd548b5aef3f888c6ce0a
Author: gregt5259 <gr...@amdocs.com>
Date: 2017-07-02T10:16:26Z
GEODE-2891: connect-timeout violation in C++ Native Client
Change time measure unit for handshake from seconds to milliseconds
----
> connect-timeout violation in C++ Native Client
> ----------------------------------------------
>
> Key: GEODE-2891
> URL: https://issues.apache.org/jira/browse/GEODE-2891
> Project: Geode
> Issue Type: Bug
> Components: native client
> Reporter: Gregory Vortman
> Attachments: GEODE-connect-timeout-violation.docx
>
>
> 1. C++ native client doesn’t honour read-timeout-milli-sec in a consistent way while connecting to a server
> 2. The lock on the connection pool has a very high granularity. Even if the client can’t connect to one server, all other threads which are working with totally different servers get affected by it
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)