[
https://issues.apache.org/jira/browse/QPID-7364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15405713#comment-15405713
]
Keith Wall commented on QPID-7364:
----------------------------------
We said we desire to change the housekeeping process to that it operates across
a fixed number of messages (configurable) before rescheduling itself if
necessary. The housekeeping algorithm currently entwines the processing of
TTL/Unholding of messages/alerts and flow to disk. We will considering
splitting these responsibilities scheduling each part separately. It will
also be possible to schedule these tasks more intelligently. For instance, an
unhold task could schedule itself so that it next runs when the next message
that requires to be unheld is due.
> Housekeeping should chunk expensive work
> ----------------------------------------
>
> Key: QPID-7364
> URL: https://issues.apache.org/jira/browse/QPID-7364
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: Future
> Reporter: Keith Wall
> Fix For: Future
>
>
> Housekeeping currently could hog resources, for instance a single run could
> TTL a very large number of messages, starving other actors in the Broker or
> delay a shutdown of a Broker or VirtualHost. It should be changed so that it
> chunks work into reasonable chunks, rescheduling itself as necessary.
> Housekeeping is also currently responsible for transaction timeout.
> Transaction timeout would be better implemented as a Ticker, which would
> awaken the connection if a idle/close timeout is due.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
