Gary, To unsubscribe, send a message to: [email protected]
and possibly To unsubscribe, send a message to: [email protected] We can not unsubscribe you - easily. Aaron On Wed, Sep 24, 2014 at 2:17 PM, Truesdale, Gary <[email protected]> wrote: > Remove- > > > Josh, can you take me off this list? > > Gary Truesdale P.E. > Account Manager > Hewlett-Packard > 310.658.0922 > > -----Original Message----- > From: Josh Thompson (JIRA) [mailto:[email protected]] > Sent: Wednesday, September 24, 2014 11:17 AM > To: [email protected] > Subject: [jira] [Resolved] (VCL-5) multiple web servers > > > [ > https://issues.apache.org/jira/browse/VCL-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Josh Thompson resolved VCL-5. > ----------------------------- > Resolution: Fixed > >> multiple web servers >> -------------------- >> >> Key: VCL-5 >> URL: https://issues.apache.org/jira/browse/VCL-5 >> Project: VCL >> Issue Type: New Feature >> Components: database, web gui (frontend) >> Affects Versions: 2.2 >> Reporter: Josh Thompson >> Fix For: 2.4 >> >> >> Modify the frontend code to allow the existence of multiple web servers >> running in a load balanced fashion. The holdup for this has been due to a >> semaphore lock around the code that allocates a machine for a reservation. >> Without the semaphore, two people hitting the site at (nearly) the exact >> same time can end up being assigned the same machine. >> An idea I came up with to handle this is to only run the scheduling portion >> of the code via the XML RPC API. A single web server would be elected as the >> master. All web servers would call the scheduling part of the code via the >> API on the master, allowing the semaphore lock to still function. If the >> master server goes down, an election process would determine the new master. > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) -- Aaron Peeler Program Manager Virtual Computing Lab NC State University All electronic mail messages in connection with State business which are sent to or received by this account are subject to the NC Public Records Law and may be disclosed to third parties.
