You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "Alexander Kolbasov (JIRA)" <ji...@apache.org> on 2017/04/29 17:37:04 UTC

[jira] [Commented] (SENTRY-1580) Provide pooled client connection model with HA

    [ https://issues.apache.org/jira/browse/SENTRY-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989967#comment-15989967 ] 

Alexander Kolbasov commented on SENTRY-1580:
--------------------------------------------

I think the best way to do it is to use pool for Thrift transports.

> Provide pooled client connection model with HA
> ----------------------------------------------
>
>                 Key: SENTRY-1580
>                 URL: https://issues.apache.org/jira/browse/SENTRY-1580
>             Project: Sentry
>          Issue Type: Sub-task
>          Components: Sentry
>    Affects Versions: sentry-ha-redesign
>            Reporter: Alexander Kolbasov
>            Assignee: Alexander Kolbasov
>            Priority: Critical
>             Fix For: sentry-ha-redesign
>
>         Attachments: SENTRY-1580.001-sentry-ha-redesign.patch
>
>
> 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).



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