4 Replies Latest reply on Apr 5, 2011 10:30 AM by Andy Taylor

    HA with replication?

    Brad Pardee Newbie

      I'm currently using 2.1.2 with 1 backup server using replication.  I was looking to upgrade but I see that 2.2.2 only supports shared store.  Is there a time frame on when it will support replication?  I don't think shared store is a viable option for us but automatic failback sure sounds nice.

       

      thanks!

        • 1. HA with replication?
          Clebert Suconic Master

          It's the next thing we will work after mavenizing it.

           

          It will be on 2.3. The plan is to release 2.3 right after we finished replication.

          • 2. HA with replication?
            Andy Taylor Master

            we'll be starting the next phase of dev soon and this is top priority, as for time frames we dont have any specific date. I would keep an eye on jira.

             

            And yeah, failback is cool, we also now support multiple backups too.

            • 3. HA with replication?
              Reid Morrison Newbie

              Are you serious?

               

              The existing replication has just been removed from the HornetQ product? Is this covered in the upgrade or even the release notes?

               

              We already have HornetQ in production with replication and failover. Not everyone can afford expensive SANs just to implement the new "failback"

              • 4. HA with replication?
                Andy Taylor Master
                Are you serious?

                Yes, i dont have a sense of humour

                 

                The existing replication has just been removed from the HornetQ product? Is this covered in the upgrade or even the release notes?

                It hasnt actually been removed from an implementation pov, but since we've changed lots of stuff it won't actually work so we have disabled this. It was either release a version now so none replication users can use it now, or wait until replication was upgraded. Either way, it makes no difference to how long a replication user would wait for a new version.