beam-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Scott Wegner <>
Subject Re: Java compiler OOMs on Jenkins/Gradle
Date Tue, 01 May 2018 23:40:06 GMT
Sorry about the instability. We need to get the Gradle jobs tuned for our
Jenkins machines, and there's no way to test my configuration changes
without affecting all jobs :-/

The changes I'm making are here:

It seems that they're still not quite right: the intent is to allocate half
the memory to each job, and then divide it up by worker. But for 16 workers
each is getting ~1GB, even though the machines have 100GB total. I suspect
I'm just calling the wrong API.

On Tue, May 1, 2018 at 1:41 PM Eugene Kirpichov <>

> Thanks! FWIW seems that my other Jenkins build is about to fail with the
> same issue
> -
> "Expiring Daemon because JVM Tenured space is exhausted"
> On Tue, May 1, 2018 at 1:36 PM Lukasz Cwik <> wrote:
>> who is currently messing around with tuning some
>> Gradle flags related to the JVM and its memory usage.
>> On Tue, May 1, 2018 at 1:34 PM Eugene Kirpichov <>
>> wrote:
>>> Hi,
>>> I've seen the same issue twice in a row on PR
>>> : the Java precommit fails
>>> with messages like:
>>> > Task :beam-sdks-java-core:compileTestJava
>>> An exception has occurred in the compiler ((version info not
>>> available)). Please file a bug against the Java compiler via the Java bug
>>> reporting page ( after checking the Bug
>>> Database ( for duplicates. Include your program
>>> and the following diagnostic in your report. Thank you.
>>> java.lang.OutOfMemoryError: GC overhead limit exceeded
>>> Full build link:
>>> Anybody know what's up with that? I thought we got new powerful Jenkins
>>> executors and we shouldn't be running out of memory? However, I see that
>>> the build specifies* -Dorg.gradle.jvmargs=-Xmx512m* - this seems too
>>> small. Should we increase this?
>>> Thanks.
>> --

Got feedback? http://go/swegner-feedback

View raw message