geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (GEODE-2891) connect-timeout violation in C++ Native Client
Date Thu, 06 Jul 2017 14:35:00 GMT


ASF GitHub Bot commented on GEODE-2891:

Github user pivotal-jbarrett commented on the issue:
    @gregt5259 This is a solution to the problem but not the solution we as committers are
comfortable committing as it directly conflicts with the correct change, which is to use type
safe durations rather than magic number math and system wide properties to create a confusing
array of time values.
    If you want this change sooner than later you could implement it using std::chrono::duration
as outlined in GEODE-3137 or maintain a fork with your change in it.

> connect-timeout violation in C++ Native Client
> ----------------------------------------------
>                 Key: GEODE-2891
>                 URL:
>             Project: Geode
>          Issue Type: Bug
>          Components: native client
>            Reporter: Gregory Vortman
>            Assignee: Jacob S. Barrett
>         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

View raw message