|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 1604 | minor | always | 02-06-07 15:08 | 09-05-07 11:46 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | |||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 3.1.3 | ||
|
|
|||||
| 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. |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||