[lvs-users] Setting Weight to 0 and still accepting connections

Sebastian Krueger sebykrueger at gmail.com
Thu Oct 30 02:56:56 GMT 2008


Hi everyone,

I have the following configuration:

quiescent=no
virtual=10.0.24.35:18007              # 10.0.24.35 == eai-rv2p
        real=10.0.24.38:18007 gate 10 # 10.0.24.38 == eai100-rv2p
        real=10.0.24.43:18007 gate 10 # 10.0.24.43  == eai200-rv2p
        persistent=3600
        checktype=negotiate
        service=http
        scheduler=lc
        protocol=tcp
        checkport=18001
        request="/dpPingApp100_servlet_archipelagoPing/archipelagoPing"
        receive="SUCCESS"

virtual=10.0.24.35:18001
        real=10.0.24.39:18001 gate 10 # 10.0.24.39 == eai110-rv2p
        real=10.0.24.44:18001 gate 10  # 10.0.24.44  == eai210-rv2p
        persistent=3600
        checktype=negotiate
        service=http
        scheduler=lc
        protocol=tcp
        checkport=18001
        request="/dpPingApp110REP_servlet_pingAppREP/pingAppREP"
        receive="SUCCESS"

According to the man page:
-w, --weight weight
              Weight is an integer specifying the capacity  of a
server relative to the others in the pool. The valid values of  weight
 are  0
              through to 65535. The default is 1. Quiescent servers
are specified with a weight of zero. A quiescent server will receive
no new
              jobs but still serve the existing jobs, for all
scheduling algorithms distributed with the Linux Virtual Server.
Setting a quies‐
              cent server may be useful if the server is overloaded or
needs to be taken out of service for maintenance.

So I read that if I set the weight of a real server to 0, then no new
connections will be accepted. And yet, I definitely am seeing new
connections being accepted. Is there anything that I have missed out?
Like if I set persistent, then the weighting is ignored?

Cheers, Sebastian.




More information about the lvs-users mailing list