|
wojciech.kapcia@tigase.net opened 1 decade ago
|
||||||
|
Good point, I think automatic switching over to slave was already in some ticket. I think this task can be combined with the general work on the new DB api. |
||||||
|
|
I do not think we can make it for 5.2.0. |
||||||
|
|
wojciech.kapcia@tigase.net batch edited 6 months ago
|
| Type |
New Feature
|
| Priority |
Blocker
|
| Assignee | |
| RedmineID |
1588
|
| Version |
Candidate for next major release
|
Iterations
Issue Votes (0)
Watchers (2)
In case of having repository on multiple machines (for example master slave setup) implement:
configuration options to setup all repository machines
fallback to slave in case master is down (i.e. connection lost and cannot be re-established)
implement some kind of occasional verification of data consistency between master and slave