activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Davies (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (AMQ-1660) Scheduled Failover
Date Sun, 28 Dec 2008 07:58:05 GMT

     [ https://issues.apache.org/activemq/browse/AMQ-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rob Davies reassigned AMQ-1660:
-------------------------------

    Assignee: Hiram Chirino

> Scheduled Failover
> ------------------
>
>                 Key: AMQ-1660
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1660
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 4.1.1, 5.0.0
>         Environment: all platforms that support a running standalone broker
>            Reporter: Rob Bugh
>            Assignee: Hiram Chirino
>             Fix For: 5.3.0
>
>
> 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

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message