Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

check_status #22

Open
glebus opened this Issue Dec 29, 2011 · 1 comment

Comments

Projects
None yet
2 participants

glebus commented Dec 29, 2011

Hello! I have a few questions.

  1. Please tell us the meaning of the fields in the table that the output of the check_status.
  2. I have this problem. There is a server written in Python / Twisted uses to connect to the web sockets. On it were sufficiently high loads, and I decided to make a cluster. Advantage of your leadership and everything turned out. Queries in round robin went on all 6 servers, but there was such probelma - after connecting to the server after a while the connection is lost and re-appears. You do not know what it can be connected?

Thank you.

uname-a
Linux 2.6.32-30-server # 59-Ubuntu SMP Tue Mar 1 22:46:09 UTC 2011 x86_64 GNU / Linux

config:

tcp {
upstream backend {
server 95.169.184.31:8044;
server 95.169.184.31:8045;
server 95.169.184.31:8046;
server 95.169.184.31:8047;
server 95.169.184.31:8048;
server 95.169.184.31:8049;
check interval = 3000 rise = 2 fall = 5 timeout = 10000;
}

server {
listen *: 8043;
tcp_nodelay on;
proxy_pass backend;
}
}

http {

     server {
             listen 9000;
             location / wstat {
                     check_status;
             }
     }

}

Owner

yaoweibin commented Dec 30, 2011

Hi,

  1. The table field meanings are:
    • Index: The server index in the check table
    • Name : The upstream server name
    • Status: The marked status of the server.
    • Busyness: The number of connections which are connecting to the
      server.(There was a typo before)
    • Rise counts: Count the successful checking
    • Fall counts: Count the unsuccessful checking
    • Access counts: Count the times accessing to this server
    • Check type: The type of the check packet
  2. I don't know the lost connection. Are the network OK? There is a
    timeout with the upstream connection. The default value is 60 seconds.

On 2011-12-29 18:59, Gleb wrote:

Hello! I have a few questions.

  1. Please tell us the meaning of the fields in the table that the output of the check_status.
  2. I have this problem. There is a server written in Python / Twisted uses to connect to the web sockets. On it were sufficiently high loads, and I decided to make a cluster. Advantage of your leadership and everything turned out. Queries in round robin went on all 6 servers, but there was such probelma - after connecting to the server after a while the connection is lost and re-appears. You do not know what it can be connected?

Thank you.

uname-a
Linux 2.6.32-30-server # 59-Ubuntu SMP Tue Mar 1 22:46:09 UTC 2011 x86_64 GNU / Linux

config:

tcp {
upstream backend {
server 95.169.184.31:8044;
server 95.169.184.31:8045;
server 95.169.184.31:8046;
server 95.169.184.31:8047;
server 95.169.184.31:8048;
server 95.169.184.31:8049;
check interval = 3000 rise = 2 fall = 5 timeout = 10000;
}

server {
listen *: 8043;
tcp_nodelay on;
proxy_pass backend;
}
}

http {

      server {
              listen 9000;
              location / wstat {
                      check_status;
              }
      }

}


Reply to this email directly or view it on GitHub:
#22

Weibin Yao

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment