incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vitaly Brodetskyi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-3071) Ambari handles limts incorrectly for non-default users
Date Mon, 02 Sep 2013 17:38:52 GMT

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

Vitaly Brodetskyi updated AMBARI-3071:
--------------------------------------

    Attachment: AMBARI-3071.patch
    
> Ambari handles limts incorrectly for non-default users
> ------------------------------------------------------
>
>                 Key: AMBARI-3071
>                 URL: https://issues.apache.org/jira/browse/AMBARI-3071
>             Project: Ambari
>          Issue Type: Bug
>          Components: agent
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>            Priority: Critical
>             Fix For: 1.4.1
>
>         Attachments: AMBARI-3071.patch
>
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> During the installation, hadoop RPMs extracts and put to /etc/security/limits.d the following
files:
> hdfs.conf, mapred.conf which lister needed limits for the users' processes.
> All works fine with default user names.
> However, if customer use non-default user names, Ambari do not renames those files accordingly.
> As a result non-default users always get default limits settings (1024) instead of "recommended"
32K...
> Needs to be fixed ASAP!!!

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

Mime
View raw message