On 4/17/2018 2:54 PM, Lukas Tribus wrote: >> Originally, the "hollywood" entry on the be-cdn-9000 backend (which you can >> see at the config I linked above) had the backup keyword. But what I >> noticed happening was that when planet went down, it took about ten >> additional seconds (no precise timing was done) for hollywood to go active, >> and during that time, the client got "no server available" messages. > > You said this is about a 502 error. But "no server available" is not a > error that haproxy emits and 503 would be "Service Unavailable". > I don't see any issue replaying this here locally with haproxy 1.5.12.
I have figured out how to resolve the difficulty I was encountering on this thread, and I can now do service restarts with zero loss. The disable-on-404 config, combined with a change to the way the init script does the restart, has fixed it. I switched gears and that part about the 'backup' keyword is for a different problem. One I already emailed the list separately on and haven't gotten a response. Feel free to drop this thread and move to the other one. Here is the message on the list archive: https://www.mail-archive.com/[email protected]/msg29615.html I apologize for any confusion. The "no server available" is something I saw in the output from curl when the primary server went down and the backup had not yet been changed to Active. I don't have a transcript of that ssh session, and right now I can't take the steps to reproduce the error -- the servers are being used heavily for something that can't be postponed, and reproducing the error would cause some of those requests to fail. Thanks, Shawn
