sentry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Ma (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (SENTRY-296) Sentry Service Client does not allow for connection pooling
Date Fri, 14 Nov 2014 03:45:33 GMT

     [ https://issues.apache.org/jira/browse/SENTRY-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Colin Ma reassigned SENTRY-296:
-------------------------------

    Assignee: Colin Ma

> Sentry Service Client does not allow for connection pooling
> -----------------------------------------------------------
>
>                 Key: SENTRY-296
>                 URL: https://issues.apache.org/jira/browse/SENTRY-296
>             Project: Sentry
>          Issue Type: Bug
>    Affects Versions: 1.4.0
>            Reporter: Lenni Kuff
>            Assignee: Colin Ma
>              Labels: grant/revoke
>
> The Sentry Service Client does not allow for connection pooling because there is no way
to:
> 1) Detect that a connection is broken
> 2) Re-open a broken connection
> This would allow for Sentry Service clients to implement connection pooling like:
> {code}
> if (!client.isOpen()) {
>   client.reopen();
> }
> {code}
> Currently, the only way to ensure connections are not broken is to open a new connection
before every RPC.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message