You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Jonathan Hurley (JIRA)" <ji...@apache.org> on 2015/10/07 23:15:26 UTC

[jira] [Reopened] (AMBARI-13307) Agent instance memory footprint likely gradually growing

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

Jonathan Hurley reopened AMBARI-13307:
--------------------------------------

I had to revert this commit. It was preventing status commands from running which would show all components as stopped even though they were running and alerts were green. 

I even deployed a new cluster thinking that it was my environment. Verified that reverting this patch resolves the problem

When I ran the status command manually on the command line, I noticed zero output from the logger, so I figured that was a good place to start. Noticed this commit which seemed to be the cause.

> Agent instance memory footprint likely gradually growing
> --------------------------------------------------------
>
>                 Key: AMBARI-13307
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13307
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.1.3
>
>
> Noticed about 1.5 G of resident memory for the agents on a cluster that is running for about a month.
> Which is an obvious memory leak.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)