flink-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Schueler, Ricarda" <Ricarda.Schue...@student.hpi.uni-potsdam.de>
Subject AW: Memory management issue
Date Tue, 08 Sep 2015 08:12:28 GMT

we tested it with the version 0.9.1, but unfortunately the issue persists.



Von: ewenstephan@gmail.com <ewenstephan@gmail.com> im Auftrag von Stephan Ewen <sewen@apache.org>
Gesendet: Montag, 7. September 2015 00:39
An: user@flink.apache.org
Betreff: Re: Memory management issue


Can you switch to version 0.9.1? That one included some bug fixes, including one or two possible
deadlock situations.

Please let us know if that solves the issue, or if the issue persists...


On Fri, Sep 4, 2015 at 7:19 PM, Ricarda Schueler <ricarda.schueler@student.hpi.uni-potsdam.de<mailto:ricarda.schueler@student.hpi.uni-potsdam.de>>

Hi All,

We're running into a memory management issue when using the
iterateWithTermination function.
Using a small amount of data, everything works perfectly fine. However,
as soon as the main memory is filled up on a worker, nothing seems to be
happening any more. Once this happens, any worker whose memory is full
will have its CPU workload drop to a minimum (<5%), while maintaining a
full memory with no apparent garbage collection happening and thus the
memory remaining full. All Tasks within this iteration are set to
started, yet none of them actually do anything measurable.
While runs with slightly less data (so that all intermediate results
barely fit into main memory) finished within minutes, runs where the
data would no longer fit would run for days with no results in sight.
When using fewer workers or even running the algorithm locally, this
issue already appears when using less data, which the larger cluster
(with more combined memory) could still handle.

Our code can be found at [1].

Best regards

[1]: https://github.com/DBDA15/graph-mining/tree/master/graph-mining-flink

View raw message