|
Comment by
Martin
[
18/Jul/16 08:17 AM
]
|
Hi Robin,
what if your nodes store most of the artifacts on the node itself, than there is not much data stored on the master itself? I was thinking to setup a NFS server and a MySQL database that will be used by the master. I was thinking to have an active/passive setup where in case of outage of the active master we could do a switch on the passive master. The switch from the active to the passive instance could be done on DNS level.
What do you think about this setup?
|
|
Comment by
Robin Shen
[
19/Jul/16 12:42 AM
]
|
|
This should work. But please be noted that at the same time, only one QB server can connect to the database. That is to say, you can only start up the inactive server after finding the active server dies.
|
|
Comment by
Martin
[
30/May/17 11:45 AM
]
|
|
Is this still valid for QB7?
|
|
Comment by
Martin
[
30/May/17 11:47 AM
]
|
|
Why is there actually the limitation that only one instance can connect to a db? I understand that only one instance should be the active one but if the other one stays passive it shouldn't be problematic
|
|
Comment by
Robin Shen
[
31/May/17 12:37 AM
]
|
|
As QB pre-loads many things from database and caches them for performance reason. Also some data such as build queue is only maintained in application memory. The passive one will not be aware of all these changes.
|
Generated at Fri Apr 19 14:32:37 UTC 2024 using JIRA 189.
