accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ACCUMULO-3257) Make Randomwalk respect timeout (maxSec) more reliably
Date Fri, 24 Oct 2014 20:43:33 GMT

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

Josh Elser resolved ACCUMULO-3257.
----------------------------------
    Resolution: Fixed

Interrupt the current Node if it executes beyond the duration of maxSec

> Make Randomwalk respect timeout (maxSec) more reliably
> ------------------------------------------------------
>
>                 Key: ACCUMULO-3257
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3257
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: test
>    Affects Versions: 1.5.2, 1.6.1
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.6.2, 1.7.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Randomwalk presently has the ability to specify a maximum execution time (in seconds)
for a module (e.g. Bulk.xml). The timeout is checked before the next node in the module is
run, but doesn't interrupt a long-running node. For extremely long test runs (hours to days)
which randomwalk is designed to perform, this is fine because running it for an extra hour
when you've been running it for 24+ already is without consequence.
> However, trying to keep a well-bounded randomwalk run with respect to time is rather
difficult, especially when the tests queue up many operations for Accumulo to work through
(intentionally bashing Accumulo to try to make it fail). 
> The concern in respecting a timeout is that verification steps may not be run and we
might miss failures that happened.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message