Hi, I guess OOM errors by the kernel, not by the JVM, right? I first thought JVM OutOfMemoryExceptions .. we could have fixed those with jvm memory parameters. But it for kernel OOM errors, we need more available memory on the build slaves. How much memory is typically available on the machines? (maybe enabling swap space is a good temporary workaround?)
Regards, Robert On Sun, Jun 5, 2016 at 10:09 PM, Márton Balassi <[email protected]> wrote: > Hi Olaf, > > I could not find the OOM's in the logs you linked, how can I reproduce > them? > > The Flink team uses Travis for CI internally [1] and the machine there is > based on the pre-2015 standard, which has 7,5 GB RAM in it [2], but I > regularly build Flink on 4GB RAM virtual images myself. How much memory do > we give it currently? > > [1] https://travis-ci.org/apache/flink/ > [2] > https://docs.travis-ci.com/user/ci-environment/#Virtualization-environments > > On Sun, Jun 5, 2016 at 9:54 PM, Olaf Flebbe <[email protected]> wrote: > > > Hi, > > > > While restarting the compile process, older logfiles have been removed. > > The Error messages where typically OOM errors. > > > > Olaf > > > > > Am 05.06.2016 um 21:44 schrieb Olaf Flebbe <[email protected]>: > > > > > > Hi, > > > > > > I am looking into why our CI stalled again. > > > > > > I am seeing a lot of out of memory conditions on slave 06 . > > > > > > It seems to me that flink is causing it : For instance > > > > > > > > > https://ci.bigtop.apache.org/job/Bigtop-trunk-packages/BUILD_ENVIRONMENTS=ubuntu-14.04,COMPONENTS=flink,label=docker-slave/229/ > > > > > > https://ci.bigtop.apache.org/job/Bigtop-trunk-packages/227/BUILD_ENVIRONMENTS=fedora-20,COMPONENTS=flink,label=docker-slave/ > > > > > > Question to the flink guys: How much memory should we reserve for a > > flink compile process ? > > > > > > Olaf > > > > >
