Description
SENTRY-1477 provided a simple connection retry model which is incompatible with the object pool. I think that we can combine the pool model in case of multiple connections by using GenericKeyedObjectPool using server address as a key. When we suspect a disconnect we can clear the whole sub-pool using clear(key).
Attachments
Attachments
Issue Links
- incorporates
-
SENTRY-1724 Remove old PoolClientInvocationHandler
- Resolved
- is blocked by
-
SENTRY-1739 Sentry Kafka tests do not stop periodic update after the test end
- Resolved
- is related to
-
SENTRY-1737 SentryTransportFactory may use incorrect kerberos principal
- Resolved
-
SENTRY-1800 Flaky testConcurrentUpdateChanges test
- Resolved
-
SENTRY-1735 Sentry Clients should not log every connection request
- Resolved
- relates to
-
SENTRY-1477 Sentry clients should retry with another server when they get connection errors
- Resolved
-
SENTRY-1592 Implement NN client failover for Sentry HA
- Resolved
-
SENTRY-296 Sentry Service Client does not allow for connection pooling
- Resolved
-
SENTRY-1579 Sentry should avoid using Proxy
- Open
- links to