[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1427) Optimize Journal for Lazy-destinations

[Clebert Suconic (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBMESSAGING-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12451542#action_12451542 ] 

Clebert Suconic commented on JBMESSAGING-1427:
----------------------------------------------

Say you have a destination without any consumer, and a consumer is not expected in days. (Say... unattended DLQs or expire Queues, or valid use cases created by the user)

No files will be reclaimed until this data is consumed, because of the linked-list effect on reclaiming.

My proposal is to have two current-files on the Journal. One for lazy-destinations configured as lazy, one for regular destinations.

With that, those messages could still be on disk for days without affect reclaiming, and transactionality won' t be affected since both files are inside the journal.

(We would need a configuration on the Addres to use this special journal).

I have tried a prototype of this solution (the patch attached), and it worked.

> 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