Full Broker fails with OOME before enforcing flow-control

EnMasseProject / enmasse

EnMasse - Self-service messaging on Kubernetes and OpenShift

https://enmasseproject.github.io

Apache License 2.0

190 stars 87 forks source link

Full Broker fails with OOME before enforcing flow-control #2159

Open k-wall opened 5 years ago

k-wall commented 5 years ago

During performance tests, I notice that if you keep publishing to a queue (I was using a small-queue), the Broker fails with an OOME (heap) before imposing flow-control on the publisher. This happened in both modes FAIL and PAGE.

This suggests to me that the 512Mi default size is too tight for pod memory is too tight.

See also #2158

lulf commented 5 years ago

This is a compromise of making it possible to deploy enmasse for evaluation in more resource constrained clusters and systemtesting on travis. We should perhaps consider deploying an infra config specifically for tests and evaluation purposes.