History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-326
Type: New Feature New Feature
Status: Open Open
Priority: Major Major
Assignee: Robin Shen
Reporter: GEICO
Votes: 9
Watchers: 2

If you were logged in you would be able to see more operations.

Quick Build with High Availability

Created: 18/Feb/08 12:56 PM   Updated: 31/May/17 12:37 AM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Environment: PROD

 Description  « Hide
Currently, QuickBuild does not support high availability configuration with Tomcat.


 All   Comments   Work Log   Change History      Sort Order:
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?

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.

Martin [30/May/17 11:45 AM]
Is this still valid for QB7?

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

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.