atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suma Shivaprasad (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ATLAS-471) Atlas Server could run out of memory due to Scala memory leak
Date Thu, 04 Feb 2016 21:19:39 GMT

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

Suma Shivaprasad updated ATLAS-471:
-----------------------------------
    Assignee: Hemanth Yamijala

> Atlas Server could run out of memory due to Scala memory leak
> -------------------------------------------------------------
>
>                 Key: ATLAS-471
>                 URL: https://issues.apache.org/jira/browse/ATLAS-471
>             Project: Atlas
>          Issue Type: Bug
>            Reporter: Hemanth Yamijala
>            Assignee: Hemanth Yamijala
>            Priority: Critical
>         Attachments: ATLAS-471-v1.patch
>
>
> We noticed our servers running OutOfMemory occasionally, particularly under heavy query
loads. Profiling the app with YourKit, I found a lot of instances of {{scala.util.parsing.combinator.Parsers}},
{{java.lang.ThreadLocal$ThreadLocalMap}} and {{org.apache.atlas.query.QueryLexer}} objects.
These object counts increase steadily over time as seen after taking multiple snapshots.



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

Mime
View raw message