You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Ken Giusti (JIRA)" <ji...@apache.org> on 2010/10/28 15:00:30 UTC
[jira] Updated: (QPID-2841) QMF: set TTL on agent heartbeat
messages
[ https://issues.apache.org/jira/browse/QPID-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ken Giusti updated QPID-2841:
-----------------------------
Fix Version/s: 0.7
> QMF: set TTL on agent heartbeat messages
> ----------------------------------------
>
> Key: QPID-2841
> URL: https://issues.apache.org/jira/browse/QPID-2841
> Project: Qpid
> Issue Type: Improvement
> Components: Qpid Managment Framework
> Environment: all
> Reporter: Ken Giusti
> Assignee: Ken Giusti
> Fix For: 0.7
>
>
> Heartbeats are issued periodically by QMF agents. Each heartbeat is stateless - there is no information loss if a heartbeat is dropped or ignored by the client. While performance testing, it was discovered that multiple heartbeats will queue up should a console be unable to consume them fast enough. Most of these heartbeats are stale: the agent has issue a new heartbeat(s) since the older heartbeat was queued. Processing these "stale" heartbeats is useless.
> By setting the TTL in heartbeat messages, stale heartbeats will be discarded by the broker instead of being sent to the console.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org