You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by "Keith Turner (Created) (JIRA)" <ji...@apache.org> on 2012/01/10 01:38:39 UTC
[jira] [Created] (ACCUMULO-297) User could delete table after
permission to do so was removed
User could delete table after permission to do so was removed
-------------------------------------------------------------
Key: ACCUMULO-297
URL: https://issues.apache.org/jira/browse/ACCUMULO-297
Project: Accumulo
Issue Type: Bug
Reporter: Keith Turner
Assignee: Keith Turner
Fix For: 1.4.0
While running the security random walk test it failed because a user could delete a table after their permission to do so was removed. I think this was a cache consistency issues. The permission was removed by tablet server A, and then the master was requested to do a remove. The permission cache update from zookeeper to the master was inflight.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (ACCUMULO-297) User could delete table after
permission to do so was removed
Posted by "Keith Turner (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACCUMULO-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Turner resolved ACCUMULO-297.
-----------------------------------
Resolution: Fixed
> User could delete table after permission to do so was removed
> -------------------------------------------------------------
>
> Key: ACCUMULO-297
> URL: https://issues.apache.org/jira/browse/ACCUMULO-297
> Project: Accumulo
> Issue Type: Bug
> Reporter: Keith Turner
> Assignee: Keith Turner
> Fix For: 1.4.0
>
>
> While running the security random walk test it failed because a user could delete a table after their permission to do so was removed. I think this was a cache consistency issues. The permission was removed by tablet server A, and then the master was requested to do a remove. The permission cache update from zookeeper to the master was inflight.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira