You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Balázs Bence Sári (JIRA)" <ji...@apache.org> on 2019/02/21 10:27:00 UTC

[jira] [Resolved] (AMBARI-25151) Support SystemD integration of Ambari agent with SLES

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

Balázs Bence Sári resolved AMBARI-25151.
----------------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: trunk)
                   2.7.4

> Support SystemD integration of Ambari agent with SLES
> -----------------------------------------------------
>
>                 Key: AMBARI-25151
>                 URL: https://issues.apache.org/jira/browse/AMBARI-25151
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-agent
>    Affects Versions: 2.6.2
>            Reporter: Balázs Bence Sári
>            Assignee: Balázs Bence Sári
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.7.4
>
>          Time Spent: 3h 20m
>  Remaining Estimate: 0h
>
> SLES 12.x uses Systemd v228 which imposes a 512 process/thread limit for processes started by ambari-agent if both ambari-agent and the process runs as root.
> The solution should be a *systemd* service unit file that sets *TasksMax=infinity* for *ambari*-agent to overcome this limitation. _TasksMax_ is a parallel mechanism to process limits, so limits will still apply.
> The ambari-agent rpm must be build with *-P suse12* in order to include the service file in the rpm.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)