You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by "John Vines (JIRA)" <ji...@apache.org> on 2012/05/16 18:03:02 UTC
[jira] [Updated] (ACCUMULO-75) Modify Security Randomwalk and test
with concurrency
[ https://issues.apache.org/jira/browse/ACCUMULO-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Vines updated ACCUMULO-75:
-------------------------------
Assignee: (was: John Vines)
This may not even be something we want to set up concurrently. We currently operate at such a high rate by running multiple independent randomwalks that we can outpace zookeeper. So this may not even be necessary, unless we can get past that hurdle.
> Modify Security Randomwalk and test with concurrency
> ----------------------------------------------------
>
> Key: ACCUMULO-75
> URL: https://issues.apache.org/jira/browse/ACCUMULO-75
> Project: Accumulo
> Issue Type: Task
> Components: test
> Affects Versions: 1.4.0, 1.3.5
> Reporter: John Vines
> Labels: concurrency, randomwalk, security, test
> Fix For: 1.5.0
>
>
> Currently the Security randomwalk test does not work against a single user space when run concurrently, so there's a guarantee that every instances will have it's own user spaces. We want to adjust it to allow a common user/set of users to be modified concurrently, to see what happens. And then we want to run it to see what breaks.
--
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