To follow up...
2) Enqueue 1048576000 or more bytes of data into the local queue on
www-1, watch it flow across the federation link to the hits queue on
queue-1.
Actually, the byteDepth of the destination queue ends up exceeding the
configured max-queue-size limit by a great deal - then the server dies
and when it is restarted the store and forward brokers aren't ever
able to forward messages over the federation link again. For
instance, at the time that I brought the destination broker back up
the recovered queue stats were as follows:
qpid: show queue 113
Object of type org.apache.qpid.broker:queue: (last sample time:
02:43:01)
Type Element 113
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
========================================================================
property vhostRef 105
property name hits_local
property durable True
property autoDelete False
property exclusive False
property arguments {u'qpid.file_size': 5120L,
u'qpid.file_count': 32L, u'qpid.policy_type': u'flow_to_disk'}
statistic msgTotalEnqueues 3309228 messages
statistic msgTotalDequeues 3309228
statistic msgTxnEnqueues 0
statistic msgTxnDequeues 0
statistic msgPersistEnqueues 3309228
statistic msgPersistDequeues 3309228
statistic msgDepth 0
statistic byteDepth 0 octets
statistic byteTotalEnqueues 2788025056
statistic byteTotalDequeues 2788025056
statistic byteTxnEnqueues 0
statistic byteTxnDequeues 0
statistic bytePersistEnqueues 2788025056
statistic bytePersistDequeues 2788025056
statistic consumerCount 1 consumer
statistic consumerCountHigh 1
statistic consumerCountLow 1
statistic bindingCount 2 bindings
statistic bindingCountHigh 2
statistic bindingCountLow 2
statistic unackedMessages 0 messages
statistic unackedMessagesHigh 0
statistic unackedMessagesLow 0
statistic messageLatencySamples 0
statistic messageLatencyMin 0
statistic messageLatencyMax 0
statistic messageLatencyAverage 0
__
Charles Woerner | [email protected] | demandbase
