ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Wagle (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-12859) AMS cache could result in OOM in ambari server
Date Fri, 20 May 2016 17:42:13 GMT

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

Siddharth Wagle updated AMBARI-12859:
-------------------------------------
    Component/s: ambari-metrics

> AMS cache could result in OOM in ambari server
> ----------------------------------------------
>
>                 Key: AMBARI-12859
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12859
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-metrics, ambari-server
>    Affects Versions: 2.1.2
>            Reporter: Siddharth Wagle
>            Assignee: Siddharth Wagle
>            Priority: Critical
>             Fix For: 2.1.2
>
>
> Requesting metrics for 1 week resulted in:
> {noformat}
> Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x00000000d28b2000,
216981504, 0) failed; error='Cannot allocate memory' (errno=12)
> #
> # There is insufficient memory for the Java Runtime Environment to continue.
> # Native memory allocation (mmap) failed to map 216981504 bytes for committing reserved
memory.
> # An error report file with more information is saved as:
> # //hs_err_pid15931.log
> {noformat}



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

Mime
View raw message