[SENTRY-296] Sentry Service Client does not allow for connection pooling

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4.0
• Fix Version/s: 1.6.0
• Labels: grant/revoke
• Assignee: Colin
• Reporter: Lenni Kuff
• Created: 12/Jun/14 19:47
• Updated: 24/May/17 00:20
• Resolved: 21/Apr/15 08:54

Description

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:

if (!client.isOpen()) {
  client.reopen();
}

Currently, the only way to ensure connections are not broken is to open a new connection before every RPC.

Issue Links

• is blocked by: SENTRY-599 Sentry service may report incorrect status when service is restarting
• is related to: SENTRY-1580 Provide pooled client connection model with HA
• is related to: SENTRY-1703 Solr-Sentry in kerberos mode makes too many KDC requests and returns unauthorized on KDC timeout
• is related to: SENTRY-704 sentry client connection pool should be reused in service level
• is related to: SENTRY-590 Client factory for generic authorization model
• is related to: SENTRY-779 Add documentation for Sentry Client Connection Pool
• links to: rb link

Sub-Tasks

• [UnitTest] In Kerberos mode, client should run under clientSubject: Resolved
• Extend SentryClient by SentryClientInvocationHandler: Resolved
• Create connection pool factory: Resolved