Bug 404701
Summary: | Control over queue expansion | ||
---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | Rajith Attapattu <rattapat+nobody> |
Component: | qpid-cpp | Assignee: | Kim van der Riet <kim.vdriet> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Kim van der Riet <kim.vdriet> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | beta | CC: | cctrieloff, jross |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-03-21 12:30:43 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Rajith Attapattu
2007-11-29 17:02:12 UTC
Question is what to do when queue depth is to deep -- do we want to add a policy in an upcoming release to close the publisher/ push back based on memory usage? Provide mechanisms/policies that allow systems to control the expansion of queues. Details to be decided by further design and debate. Assigned to Kim, as he is working this feature Carl. |