Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
Date: Wed, 16 May 2012 14:23:02 +0000 (UTC)
From: "John Vines (JIRA)" <jira@apache.org>
To: dev@accumulo.apache.org
Message-ID: 
 <1897047066.4097.1337178182481.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1068647362.50383.1336672610337.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (ACCUMULO-585) Complain loudly when env file is
 missing
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ACCUMULO-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276763#comment-13276763 ] 

John Vines commented on ACCUMULO-585:
-------------------------------------

I'm not disagreeing that it would be good, but I'm wondering if that's something we really need to get done in the 1.4 branch. I imagine a lot will change with the refactor of the scripts in 1.5
                
> Complain loudly when env file is missing
> ----------------------------------------
>
>                 Key: ACCUMULO-585
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-585
>             Project: Accumulo
>          Issue Type: Bug
>          Components: scripts
>    Affects Versions: 1.4.0
>            Reporter: John Vines
>            Assignee: John Vines
>             Fix For: 1.4.1
>
>
> With the creation of example configurations, we made it really easy for users to get started. Unfortunately, we also took away the default nature to copy a configuration and move on. This can lead to problems when a user tried to run it out of the box without any sort of configuration. It will default to using 5 or 10g of memory total, without the user being aware of it until things start swapping.
> Now that we have the sample configurations, if accumulo-env.sh isn't there, we should error out instead of poorly guestimating these values.

--
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