Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 90121119A6 for ; Sat, 19 Apr 2014 04:27:19 +0000 (UTC) Received: (qmail 48742 invoked by uid 500); 19 Apr 2014 04:27:19 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 48654 invoked by uid 500); 19 Apr 2014 04:27:17 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 48437 invoked by uid 99); 19 Apr 2014 04:27:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 19 Apr 2014 04:27:15 +0000 Date: Sat, 19 Apr 2014 04:27:14 +0000 (UTC) From: "David Medinets (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (ACCUMULO-75) Modify Security Randomwalk and test with concurrency MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Medinets resolved ACCUMULO-75. ------------------------------------ Resolution: Not a Problem The last comment was almost a year ago. Please reopen and comment if interested continues. > 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 > Reporter: John Vines > Labels: concurrency, randomwalk, security, test > > 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 was sent by Atlassian JIRA (v6.2#6252)