ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Qiang Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Created] (RANGER-2052) The Ranger admin supports high availability
Date Thu, 29 Mar 2018 08:38:00 GMT
Qiang Zhang created RANGER-2052:
-----------------------------------

             Summary: The Ranger admin supports high availability
                 Key: RANGER-2052
                 URL: https://issues.apache.org/jira/browse/RANGER-2052
             Project: Ranger
          Issue Type: New Feature
          Components: admin
            Reporter: Qiang Zhang
            Assignee: Qiang Zhang


In real business environment, such as banks application and so on,  we should use other Ranger
service to continuely supply service once  a Ranger service exits abnormally. We call the
feature as high availability. The Ranger high availability includes:
1. The Ranger admin is high availability;
2. The mysql service that saves meta data is high availability.

For the Ranger admin high availability our scheme is as following:
1. Add a configuration item in plugin. The configuration item includes two the address of
the Ranger admin service.
2. The plugin refreshed policy from other Ranger admin service once it refresh policy from
a Ranger admin service fail.

For the mysql service that saves meta data admin high availability, our scheme is as following:
1. Add a configuration item in the Ranger admin. The configuration item includes two the address
of the mysql service.
2. Build two jdbc connection pools. The other will be used once a jdbc connection fail.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message