[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1427) Journal files can be prevented from being reclaimed if there are no, or slow consumers

[Clebert Suconic (JIRA)]

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

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

I was playing with some scenarios, and I'm not sure if the compactor would work also. I have been playing with examples and it would be possible to create scenarios where compacting is useless... Besides we would have a lot of complexity on reallocating files and hole-detection on the transaction summary.

In my opinion would be better to have a currentFile for each address on the journal. It would be the same as having one journal for each address but without loosing transactionality when sending to multiple transactions. (Which would be my initial approach with a slight variation). This option would have a better performance as we wouldn't have the compactor competing with Adds.

There won't simply be a need to compact anything.

I will bring this discussion online on our next meeting and make a post on dev forums afterwards.

> 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