Description
We need to have client failover logic for Generic service clients and Name Node clients. Currently only db policy clients have it implemented.
Attachments
Attachments
Issue Links
- blocks
-
SENTRY-1681 SentryHdfsServiceException is an unchecked exception
- Resolved
- breaks
-
SENTRY-1766 Generic model clients using kerberos can no longer connect to Sentry server
- Resolved
- depends upon
-
SENTRY-1639 Refactor thrift clients configuration constants
- Resolved
- incorporates
-
SENTRY-1592 Implement NN client failover for Sentry HA
- Resolved
- is duplicated by
-
SENTRY-1592 Implement NN client failover for Sentry HA
- Resolved
- is related to
-
SENTRY-1411 The sentry client should retry RPCs if it gets a SentryStandbyException (SentryPolicyServiceClient - pool version)
- Resolved
-
SENTRY-1736 Generic service client should support Kerberos
- Resolved
-
SENTRY-1737 SentryTransportFactory may use incorrect kerberos principal
- Resolved
-
SENTRY-1738 Inefficient connection management by retrying invocation handler
- Resolved
-
SENTRY-1735 Sentry Clients should not log every connection request
- Resolved
-
SENTRY-1568 Develop automated test for client failover
- Open
-
SENTRY-1614 DB schema key is too long for MySQL
- Resolved
-
SENTRY-1681 SentryHdfsServiceException is an unchecked exception
- 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-501 High availability for the SENTRY service(Zookeeper part)
- Resolved
- links to