For each active subscriber, Mesos master / slave maintains an event queue, which grows over time if the subscriber does not read fast enough. As the number of such "slow" subscribers grows, so does Mesos master / slave memory consumption, which might lead to an OOM event.
Ideas to consider:
- Restrict the number of subscribers for the streaming APIs
- Check (ping) for inactive or "slow" subscribers
- Disconnect the subscriber when there are too many queued events in memory