Bill Burcham created GEODE-8299:
-----------------------------------
Summary: when an SNI proxy drops connections Geode benchmarks fail
Key: GEODE-8299
URL: https://issues.apache.org/jira/browse/GEODE-8299
Project: Geode
Issue Type: Bug
Components: client/server
Reporter: Bill Burcham
In developing the SNI topology support for the benchmarks in the
{{geode-benchmarks}} repo, we noticed that when we configured the SNI proxy
(HAproxy) with timeouts (e.g. 1 second or 10 seconds), the benchmark code would
crash.
To work around the issue, for purposes of benchmarking, we turned off those
timeouts. By leaving connection and request and response timeouts unspecified,
HAproxy essentially makes the timeouts infinite—connections are never timed out.
While we haven't dug deep enough into the issue to know for sure if it is a
Geode product issue or an HAproxy one, or some problem in the benchmark logic,
it seemed prudent to open a ticket to ensure this issue is not swept under the
rug.
[~jbarrett] suspects that there might be a problem with the Geode client
connection pool logic—that perhaps when the proxy closes a connection, the
corresponding connection in the pool is not being removed correctly, or it's
not being removed quickly enough. But this is only a suspicion. It needs more
investigation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
