[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1427) Journal files can be prevented from being reclaimed if there are no, or slow consumers
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1427?page=com.atlassian.ji...
]
Clebert Suconic commented on JBMESSAGING-1427:
----------------------------------------------
Actually, never mind about what I said. There are issues with one file per Address (if you
have thousand addresse -> thousand files)
I have a few edge cases to deal with. I will make some posts about my findings on monday.
Journal files can be prevented from being reclaimed if there are no,
or slow consumers
--------------------------------------------------------------------------------------
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