[
https://issues.apache.org/jira/browse/ATLAS-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133054#comment-15133054
]
Suma Shivaprasad commented on ATLAS-471:
----------------------------------------
[~yhemanth] LGTM. One question - The spark patch is protecting the scan and
lexical initialization in a sync block where as we dont have that and they also
seem to be using 2.10 scala at that point. How did you get to know it is
threadsafe?
> 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
> 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)
