You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "michael goulish (JIRA)" <ji...@apache.org> on 2018/10/18 17:49:00 UTC
[jira] [Commented] (DISPATCH-959) Rate limiting policy
[ https://issues.apache.org/jira/browse/DISPATCH-959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16655668#comment-16655668 ]
michael goulish commented on DISPATCH-959:
------------------------------------------
This is not a bug, it's a new feature.
> Rate limiting policy
> --------------------
>
> Key: DISPATCH-959
> URL: https://issues.apache.org/jira/browse/DISPATCH-959
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Policy Engine, Routing Engine
> Affects Versions: 1.0.1
> Reporter: Chuck Rolke
> Priority: Major
> Fix For: Backlog
>
>
> Router administrators would like rate-limiting policies to allow different classes of users. A network-rate limit similar to how home cable networks are provisioned for bandwidth is a classic model and is being considered as the first choice.
> A message-per-second limit might be easier to enforce. But a single user message may have a large data section, or have a small data section but have huge message annotations. Thus a user might consume a lot of network bandwidth with only a few messages.
> It is still unclear at what level the rate limiting should be applied. Choices are:
> * Per vhost
> * Per vhost connection
> * Per vhost user
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org