[jboss-jira] [JBoss JIRA] (WFLY-1563) Wildfly functionality for removing HornetQ journal

[Jeff Mesnil (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Mesnil resolved WFLY-1563.
-------------------------------
    Resolution: Won't Fix


As HornetQ is now in maintenance mode, this new feature request will not be implemented

> Wildfly functionality for removing HornetQ journal
> --------------------------------------------------
>
>                 Key: WFLY-1563
>                 URL: https://issues.jboss.org/browse/WFLY-1563
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: JMS
>    Affects Versions: 8.0.0.Alpha1
>            Reporter: Florin Slev
>            Assignee: Jeff Mesnil
>            Priority: Minor
>
> I believe that it would be useful a feature for removing the HornetQ journal files in case of removing a Live-Backup configuration.
> Right now if you setup a HornetQ Live-Backup configuration using replication, both live and backup servers will have the same journal data.
> If you want to get rid of the live-backup configuration (via CLI: backup=false) in order to use the two servers as normal cluster nodes and restart them, they will be both seen as "live"s and will continuosly log warnings due to the fact they have same journal data. In order to remediate this problem, you have to manually remove the journal folders from the backup server in order to restart with a "fresh" journal. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)