You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Marco Didonna (Created) (JIRA)" <ji...@apache.org> on 2011/12/18 11:44:32 UTC

[jira] [Created] (WHIRR-453) Add documentation about the default settings whirr automatically adds to a particular service

Add documentation about the default settings whirr automatically adds to a particular service
---------------------------------------------------------------------------------------------

                 Key: WHIRR-453
                 URL: https://issues.apache.org/jira/browse/WHIRR-453
             Project: Whirr
          Issue Type: Improvement
    Affects Versions: 0.6.0
            Reporter: Marco Didonna


As the most experienced whirr user know whirr as a set of default properties for each service. The rationale of this quite understandable: if you don't like a default setting you can override it. But there's a catch: many non experienced user may not even know about this whirr behavior. They may think: "If I do not set this property it will default to the hadoop (or other service) default". For example

The mapred.child.ulimit is not set in the hadoop default settings. Whirr sets this value to 1.5Gb.

A user like me went crazy in order to understand why the map and reduce jvm were being killed, having -Xmx1g each as parameter.
I just had no idea whirr had its own default parameters.

So I think it's crucial to have something like http://hadoop.apache.org/common/docs/current/mapred-default.html in order to be 100% aware of whirr's behavior about the default settings.

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