[
https://jira.jboss.org/jira/browse/JBMESSAGING-1427?page=com.atlassian.ji...
]
Tim Fox commented on JBMESSAGING-1427:
--------------------------------------
I don't believe the lazy destination approach will work, since the user will need to
know in advance which destinations are lazy and which are not, which may not always be
possible.
Also if there is a slow and a fast consumer on a queue for a long time, and the slow
consumer only acks intermittently, you still have the same problem.
Instead what we need to do is create a compactor.
The compactor is an extension of the reclaimer. Files can be marked as
"tocompact" by the compactor if more than X% of the file is not needed.
A separate compactor thread then checks the "tocompact" flag and compacts
multiple files into smaller number
Optimize Journal for Lazy-destinations
--------------------------------------
Key: JBMESSAGING-1427
URL:
https://jira.jboss.org/jira/browse/JBMESSAGING-1427
Project: JBoss Messaging
Issue Type: Feature Request
Affects Versions: 2.0.0 Alpha
Reporter: Clebert Suconic
Assignee: Clebert Suconic
Fix For: 2.0.0 Beta
Attachments: optimize-lazy-destinations.patch
If a destination is lazy, not consuming messages for a long time, the journal will grow
until those messages are consumed.
This would be a problem with DLQs or messages taking days before they are consumed.
Since we inform the TransactionSummary on commits, we could change the journal to support
multiple current-files based on configuration.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira