Uploaded image for project: 'ActiveMQ Classic'
  1. ActiveMQ Classic
  2. AMQ-1660

Scheduled Failover

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Abandoned
    • 4.1.1, 5.0.0
    • NEEDS_REVIEW, AGING_TO_DIE
    • Broker
    • all platforms that support a running standalone broker

    Description

      I am using a JDBC Master/Slave topology. I'm using Postgres as the db and noticed that due to the long running transaction of the master holding the lock on the activemq_lock table my vacuums are not cleaning as many dead tuples as they could. If you are familiar with postgres then you know that vacuum can only recover dead tuples up to the point of the oldest transaction. My activemq database is on the same db server as my production db.

      So I would like to regularly failover the master to the slave to keep the lock transaction timestamp moving forward in time.

      Is there any facility built into activemq that would allow me to schedule a restart of a broker? For example, it would be nice to have the ability to specify in the broker.xml a TTL value that would mean run for this much time then restart yourself (or shutdown).

      Rob

      Attachments

        Activity

          People

            mattrpav Matt Pavlovich
            robbugh@earthlink.net Rob Bugh
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: