Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Incomplete
-
None
-
None
-
None
-
None
Description
We currently use ZooKeeper to store the user database (name and password) in addition to the authorizations and permissions for each user.
ZooKeeper is designed for distributed configuration and synchronization/coordination tasks; it is not designed to be a persistent store. In this case it would be better to use a table to manage this information.
I think this might reduce some complexity in managing that database, notably better recovery if ZK dies for some reason. Having a table might trivialize import/export of the user database (ACCUMULO-1722 is what made me think of this).