You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Bill Havanki (JIRA)" <ji...@apache.org> on 2014/01/17 15:22:19 UTC

[jira] [Resolved] (ACCUMULO-2211) Security randomwalk fails "User doesn't exist and they SHOULD"

     [ https://issues.apache.org/jira/browse/ACCUMULO-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bill Havanki resolved ACCUMULO-2211.
------------------------------------

    Resolution: Fixed

Security randomwalk has run for 10 hours so far without trouble.

> Security randomwalk fails "User doesn't exist and they SHOULD"
> --------------------------------------------------------------
>
>                 Key: ACCUMULO-2211
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2211
>             Project: Accumulo
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 1.4.4, 1.5.0
>            Reporter: Bill Havanki
>            Assignee: Bill Havanki
>            Priority: Minor
>              Labels: randomwalk, test
>             Fix For: 1.4.5, 1.5.1, 1.6.0
>
>
> The CreateUser node in the Security randomwalk test can create the "table" user even in the face of an expected PERMISSION_DENIED error. When that happens, and the next node happens to want to change the new table user's password, you can get:
> {noformat}
> org.apache.accumulo.core.client.AccumuloException: User table_server_domain_com_29780_1389915181300 doesn't exist and they SHOULD.
> {noformat}
> This happens because there is no delay between the user creation and the password change, as there are for other user creations, added in ACCUMULO-1123.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)