[
https://issues.apache.org/jira/browse/ATLAS-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133402#comment-15133402
]
Hemanth Yamijala commented on ATLAS-471:
----------------------------------------
[~suma.shivaprasad], I did notice the Spark patch introduced a synchronized
block around the parse method. I am hesitant to do that given that it might
regress performance of queries - but maybe it is safer to do that and measure.
The second reference in my list
(http://searler.github.io/2014/01/26/working-around-scala-parser-memory-leak.html)
is one place where they've mentioned:
bq. The last fix replaced the thread safety issue with a memory leak.
Anyway, I'll research some more today.
> 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)
