HAproxy turns on multicore part 503

in the regular configuration, if a single core is used for stable operation, an occasional 503 occurs when the multi-core mode is enabled, and there is no X-Server response header information.

global
    daemon
    -sharp  503
    -sharp nbproc 12
    log 127.0.0.1 local0
defaults
    log global
    mode http
    maxconn 1000000
    timeout tunnel 3600s
    timeout connect 3s
    timeout client 60s
    timeout server 60s
listen stats
  bind :9000
  mode http
  stats enable
  stats realm Haproxy\ Statistics
  stats uri /haproxy_stats
  stats auth admin:123
frontend im-proxy
    log global
    bind *:80
    default_backend server
backend server
    server web1 127.0.0.1:7002 
    http-response set-header X-Server web1

Haproxy

Jan.27,2022

Previous: Two vuecli projects interact with each other

Next: The JS callback function is not valid for variable assignment

There are three servers with different configurations. Load balancers use weighted polling. What is the weight of each server?
description : WEB project, which has three servers: A.2 core 6G memory 50G disk B.2 core 6G memory 50G disk C.2 core 4G memory 40G disk load balancing uses weighted polling. question how much weight should be given to each machine? ...

Java backend nginx haproxy

Sep.22,2021
I would like to ask, the request for calling through the nginx payload interface cannot be requested, and it can be called normally with haproxy. Why?
problem description currently there is an interface based on soap protocol. If I use nginx to configure the load call, I will not be able to connect the error is as follows. I can check the wsdl normally in the browser. then I use haproxy as the l...

Haproxy nginx java

Jul.11,2022