[ https://issues.apache.org/jira/browse/AMBARI-25151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16772820#comment-16772820 ]
Hudson commented on AMBARI-25151: --------------------------------- SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #426 (See [https://builds.apache.org/job/Ambari-branch-2.7/426/]) AMBARI-25151 SystemD support for ambari-agent on SLES12 (benyoka) (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=f0153c5c90f47d1df2f816b8f8e195880e931bae]) * (add) ambari-agent/conf/unix/ambari-agent.service * (edit) ambari-agent/src/packages/tarball/all.xml * (edit) ambari-agent/pom.xml > 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: trunk > > 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)