You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2014/12/02 00:04:12 UTC

[jira] [Commented] (ACCUMULO-3375) Move user and permission data into a table

    [ https://issues.apache.org/jira/browse/ACCUMULO-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14230648#comment-14230648 ] 

Josh Elser commented on ACCUMULO-3375:
--------------------------------------

Full disclosure, I haven't actually looked into the level of effort to make such a change. It came up in discussion once when I was talking about how Accumulo manages its user database and that ZK doesn't come across architecturally as good choice. Wanted to get it written down before I forgot again.

> Move user and permission data into a table
> ------------------------------------------
>
>                 Key: ACCUMULO-3375
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3375
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: Josh Elser
>
> 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).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)