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 9FB6717547 for ; Sat, 4 Apr 2015 02:23:34 +0000 (UTC) Received: (qmail 61079 invoked by uid 500); 4 Apr 2015 02:23:34 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 61039 invoked by uid 500); 4 Apr 2015 02:23:34 -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 61024 invoked by uid 99); 4 Apr 2015 02:23:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Apr 2015 02:23:34 +0000 Date: Sat, 4 Apr 2015 02:23:34 +0000 (UTC) From: "Josh Elser (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ACCUMULO-780) Accumulo should have a configurator 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-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated ACCUMULO-780: -------------------------------- Fix Version/s: (was: 1.7.0) 1.8.0 > Accumulo should have a configurator > ----------------------------------- > > Key: ACCUMULO-780 > URL: https://issues.apache.org/jira/browse/ACCUMULO-780 > Project: Accumulo > Issue Type: New Feature > Components: scripts > Reporter: John Vines > Fix For: 1.8.0 > > Attachments: ACCUMULO-780.v1.patch > > > We currently have a few different footprints available for users. We should use those as a base and allow users to quickly and conveniently configure their system for whatever size footprint they want. We can use the current as a baseline and extrapolate/interpolate for whichever setup they're using. This way we don't have to worry about maintaining a bunch of different sizes and instead just have an algorithm that needs occasional loving. -- This message was sent by Atlassian JIRA (v6.3.4#6332)