On 10 Apr 2008, at 16:55, Rob Bugh wrote:
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 very effective.
If you
are familiar with posgres then you know that vacuum can only recover
dead
tuples up to the point of the oldest transaction.
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
--
View this message in context:
http://www.nabble.com/Scheduled-Failover-tp16609623s2354p16609623.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
That sounds like a nice enhancement ! - could you raise a jira ?
cheers,
Rob
http://open.iona.com/ -Enterprise Open Integration
http://rajdavies.blogspot.com/
