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.

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

NSQ how to deal with different throughput queue chains? #796

Closed
jannickj opened this issue Oct 10, 2016 · 3 comments
Closed

NSQ how to deal with different throughput queue chains? #796

jannickj opened this issue Oct 10, 2016 · 3 comments
Labels

Comments

@jannickj
Copy link

jannickj commented Oct 10, 2016

I have looked through all the documentation and this problem is not mentioned anywhere not even in the 5 situations it can fail

If I have a system of two queues that are dependent on each other and the first grows faster than the second. Then I risk running out of disk space... Is it assumed that I have infinite disk space? That is not the case in my setup.

The real problem occurs if both topics are on the same machine then I will eventually be unable to post to the second queue and hit a hard deadlock.

@jehiah
Copy link
Member

jehiah commented Oct 10, 2016

@jannickj This is a good question for the mailing list nsq-users@googlegroups.com

NSQ is designed to be a distributed data stream which means that capacity constraints can be solved by scaling horizontally. It's outside the scope of NSQ to mange appropriate capacity for your specific workload.

@jehiah jehiah closed this as completed Oct 10, 2016
@jannickj
Copy link
Author

@jehiah Yes that would be outside its scope, however just being able to limit total queue size seemes like a faily simple solution.

@jehiah
Copy link
Member

jehiah commented Oct 10, 2016

That feature is being tracked as #549

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants