You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Idcmp (JIRA)" <ji...@apache.org> on 2012/07/01 00:27:42 UTC
[jira] [Created] (APLO-219) Allow fine grain control over making
space in a full queue.
Idcmp created APLO-219:
--------------------------
Summary: Allow fine grain control over making space in a full queue.
Key: APLO-219
URL: https://issues.apache.org/jira/browse/APLO-219
Project: ActiveMQ Apollo
Issue Type: Improvement
Reporter: Idcmp
As a follow up to APLO-76, it would be nice if a full queue could be safely handed to something which could walk the queue and make raw, intelligent changes to it.
Scenario: A ptp queue has multiple types of events in it and becomes full due to a slow consumer. Being able to walk the queue would allow dropping all events of a specific type in the queue and replace the first one in the queue with an event which effectively says to the consumer that they have missed events of a specific type and require to resync. The "walking", resync and replacement event would be application specific.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (APLO-219) Allow fine grain control over making
space in a full queue.
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiram Chirino updated APLO-219:
-------------------------------
Component/s: apollo-broker
Fix Version/s: wish-list
> Allow fine grain control over making space in a full queue.
> -----------------------------------------------------------
>
> Key: APLO-219
> URL: https://issues.apache.org/jira/browse/APLO-219
> Project: ActiveMQ Apollo
> Issue Type: Improvement
> Components: apollo-broker
> Reporter: Idcmp
> Fix For: wish-list
>
>
> As a follow up to APLO-76, it would be nice if a full queue could be safely handed to something which could walk the queue and make raw, intelligent changes to it.
> Scenario: A ptp queue has multiple types of events in it and becomes full due to a slow consumer. Being able to walk the queue would allow dropping all events of a specific type in the queue and replace the first one in the queue with an event which effectively says to the consumer that they have missed events of a specific type and require to resync. The "walking", resync and replacement event would be application specific.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (APLO-219) Allow fine grain control over making
space in a full queue.
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13405207#comment-13405207 ]
Hiram Chirino commented on APLO-219:
------------------------------------
Another approach might be to generate a topic even when a condition like that occurs. That way you can use a standard messaging app to implement the draining/consolidation.
> Allow fine grain control over making space in a full queue.
> -----------------------------------------------------------
>
> Key: APLO-219
> URL: https://issues.apache.org/jira/browse/APLO-219
> Project: ActiveMQ Apollo
> Issue Type: Improvement
> Components: apollo-broker
> Reporter: Idcmp
> Fix For: wish-list
>
>
> As a follow up to APLO-76, it would be nice if a full queue could be safely handed to something which could walk the queue and make raw, intelligent changes to it.
> Scenario: A ptp queue has multiple types of events in it and becomes full due to a slow consumer. Being able to walk the queue would allow dropping all events of a specific type in the queue and replace the first one in the queue with an event which effectively says to the consumer that they have missed events of a specific type and require to resync. The "walking", resync and replacement event would be application specific.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira