Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Broker crash due to slow subscriber client. #860

Closed
sanket-kulkarni-vmware opened this issue Jan 12, 2017 · 0 comments
Closed

Broker crash due to slow subscriber client. #860

sanket-kulkarni-vmware opened this issue Jan 12, 2017 · 0 comments
Assignees
@emqplus
Labels
Enhancement wontfix
Milestone
2.1 - Deploy Anyw...

Comments

@sanket-kulkarni-vmware
Copy link

Environment

  • OS: Ubuntu 16.04 LTS
  • Erlang/OTP: Erlang/OTP 19
  • EMQ: 2.0.5

I experienced broker crash when there is slow subscriber client.

For e.g
10000 Publisher clients- Publishing messages on the topic test/mqtt at the rate of 1 msg/sec.

1 Subscriber client- Subscribed to Topic test/# and consuming the messages with speed 1000 messages/second.

I experienced the Broker crash due to memory exhaustion on the broker.

Subscriber clean session flag is True.

Is there any config option for the broker to specify the queue limit for number messages to hold in a memory for the each client?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@emqplus emqplus

Labels
Enhancement wontfix
Projects
None yet
Milestone
2.1 - Deploy Anywhere, Syslog and BugFix
Development

No branches or pull requests
2 participants
@emqplus @sanket-kulkarni-vmware