[
https://issues.apache.org/jira/browse/SENTRY-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504478#comment-14504478
]
Dapeng Sun commented on SENTRY-296:
-----------------------------------
Thank [~prasadm], I will rebase the patch and do the pre-commit test.
> 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
> Attachments: SENTRY-296.001.patch, SENTRY-296.002.patch,
> SENTRY-296.003.patch, SENTRY-296.004.patch, SENTRY-296.005.patch,
> SENTRY-296.006.patch, SENTRY-296.007.patch, SENTRY-296.008.patch,
> SENTRY-296.009.patch, SENTRY-296.010.patch, SENTRY-296.011.patch
>
>
> 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)
