实现有价值的IT服务
全部博文(709)
分类: 系统运维
2006-06-23 10:56:39
configuration documentation is at .
Contents |
directive | description | default |
---|---|---|
id | unique identifier of the cluster | "" |
cluster-ref | use the values from a directive | |
client-live-time | how long the load-balancer should keep an idle socket open | 30s |
client-dead-time | how long the load-balancer should treat a backend as dead | 30s |
client-read-timeout | timeout of load-balancer reads | 30s |
client-write-timeout | timeout of load-balancer writes | |
<> | configures an srun port |
directive | description | default |
---|---|---|
id | unique identifier of the cluster definition | "" |
client-live-time | how long the load-balancer should keep an idle socket open | 30s |
client-dead-time | how long the load-balancer should treat a backend as dead | 30s |
client-read-timeout | timeout of load-balancer reads | 30s |
client-write-timeout | timeout of load-balancer writes | |
<> | configures an srun port |
Clustering and load balancing is configured in a
A cluster with two machines might look like:
... ... 30s
Load balancing has two sets of time outs, one set from the client (front-end) perspective, and one set from the server (back-end) perspective.
The client timeouts are configured directly in the
client-read-timeout | How long the frontend should wait on a read before timing out | 60s |
client-write-timeout | How long the frontend should wait on a write before timing out | 60s |
client-live-time | How long the frontend should keep a socket alive before discarding it | 60s |
client-dead-time | How long the frontend should treat a backend as dead before retrying | 15s |
60s
The server timeouts specify how long the backend will wait for new data from a frontend before giving up. This timeout should be longer than the client-live-time.
read-timeout | How long the backend should wait on a read before timing out | 30s |
write-timeout | How long the backend should wait on a write before timing out | 30s |
... ...