[ https://issues.apache.org/jira/browse/ACCUMULO-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13942134#comment-13942134 ]
John Vines commented on ACCUMULO-2508: -------------------------------------- User passwords are a cached item so there is an expected propagation delay. So this seems fine. > Security randomwalk fails "BAD_CREDENTIALS - Username or Password is Invalid" > ----------------------------------------------------------------------------- > > Key: ACCUMULO-2508 > URL: https://issues.apache.org/jira/browse/ACCUMULO-2508 > Project: Accumulo > Issue Type: Test > Components: test > Affects Versions: 1.4.4, 1.5.1 > Reporter: Bill Havanki > Assignee: Bill Havanki > Priority: Trivial > Labels: randomwalk, test > Fix For: 1.4.5, 1.5.2, 1.6.0 > > > Running security randomwalk, got this: > {noformat} > 15 11:31:36,849 [randomwalk.Module$Dummy] DEBUG: dummy.YesUserYesTable > ... > 15 11:31:36,891 [randomwalk.Module$Dummy] DEBUG: dummy.NoUserYesTable > 15 11:31:36,895 [randomwalk.Module] DEBUG: Properties for node: > TableChangeTablePass > ... > 15 11:31:36,897 [randomwalk.Framework] ERROR: Error during random walk > java.lang.Exception: Error running node Security.xml > ... > Caused by: java.lang.Exception: Error running node TableChangeTablePass > ... > Caused by: org.apache.accumulo.core.client.AccumuloSecurityException: Error > BAD_CREDENTIALS - Username or Password is Invalid > {noformat} > The table user had just been dropped, but ZK didn't have enough time to > notice (under 50 ms). This can be fixed by adding a delay after the user > being dropped, as was done for user creation under ACCUMULO-1123 and > ACCUMULO-2211. -- This message was sent by Atlassian JIRA (v6.2#6252)