JobManager container is running beyond physical memory limits
after switching from 1.4.2. to 1.5.2 we started to have problems with JM
Our use case is as follows:
- we get request from user
- run DataProcessing job
- once finished we store details to DB
We have ~1000 jobs per day. After version update our container is dying
after ~1-2 days. Previously it was running weeks without a problem.
we reduced our *web.history* from 100 to 32, but that didnt help a lot.
Do you have any suggestions what we could do? JM has 4GB memory assigned. We
will test today with increasing it to 5 or 6GB but i have a feeling that it
will only delay moment of crash
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/