Mantis Bugtracker

Viewing Issue Simple Details Jump to Notes ] View Advanced ] Issue History ] Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0001604 [Resin] minor always 02-06-07 15:08 09-05-07 11:46
Reporter ferg View Status public  
Assigned To ferg
Priority normal Resolution fixed  
Status closed   Product Version
Summary 0001604: database backup
Description (rep by Rich Dredge)

The scenario we are trying to address is failing over from one database to another without having to do a rolling restart across the application cluster. The most idea scenario is one that we can invoke a JMX operation to swing from one database server to another.
If we add multiple Driver entries to a data source, is it possible to enable/disable the driver entries at runtime?
Upon reviewing your documentation, I don't see anything that supports this, but was wondering if we could do something creative to achieve the same result using out of the box features.
An idea...could we incorporate some sort of ping query that can always fail on the standby server until the standby server is "enabled for traffic" as a primary server?
It would be very useful to add something to the DB connection pool to help in this scenario, it is something that has caused us many issues in the past.
Additional Information
Attached Files

- Relationships

- Notes
09-05-07 11:46


- Issue History
Date Modified Username Field Change
02-06-07 15:08 ferg New Issue
09-05-07 11:46 ferg Note Added: 0002269
09-05-07 11:46 ferg Assigned To  => ferg
09-05-07 11:46 ferg Status new => closed
09-05-07 11:46 ferg Resolution open => fixed
09-05-07 11:46 ferg Fixed in Version  => 3.1.3

Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
28 total queries executed.
25 unique queries executed.
Powered by Mantis Bugtracker