Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Mon, 15 Oct 2012 20:03:02 +0000 (UTC)
From: "Keith Turner (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <1260076483.47007.1350331383189.JavaMail.jiratomcat@arcas>
In-Reply-To: <1475298182.161624.1349299869692.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (ACCUMULO-784) agitator maxkill/minkill issue
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Keith Turner updated ACCUMULO-784:
----------------------------------

    Status: Patch Available  (was: Open)

I just did a search for tickets with Attachment count > 0 that were not in patch available state... found this and some other tickets

changing status to patch available....
                
> agitator maxkill/minkill issue
> ------------------------------
>
>                 Key: ACCUMULO-784
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-784
>             Project: Accumulo
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 1.5.0
>            Reporter: Chris McCubbin
>            Assignee: John Vines
>            Priority: Minor
>         Attachments: accumulo784patch.diff
>
>
> agitator.pl has a bug where if it is launched with a maxkill value and a minkill value, if the maxkill is lowered automatically by the script to the number of actual tservers, and the maxkill is then lower than the input minkill, the script can hang.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira