Changes between Version 11 and Version 12 of InstallationGuidelines/Cluster

Timestamp:

11/30/17 11:48:47 (5 years ago)

Author:

Dominic König

Comment:

--

InstallationGuidelines/Cluster

@@ -64 +64 @@
 But that isn't the case - most of the time, the first worker succeeds in much less than half a second, so it becomes available again before the next request comes in. That way, the load distribution is rather uneven (60%-25%-10%-5%) across the workers, and in low-traffic times, the last worker or even the last two may indeed be idle for hours.
 === Solution ===
-The solution is to set a much shorter tcp_keepalives_idle in postgresql.conf,
-i.e. shorter than the router timeout - then the router won't drop the
-connections even if the worker never does anything, and libpq will never get
-stuck.
+The solution is to set a much shorter {{{tcp_keepalives_idle}}} in postgresql.conf (it's turned off by default, falling back to Debian's system default of 7200sec), i.e. shorter than the router timeout - then the router won't drop the connections even if the worker never does anything, and libpq will never get stuck.
 
 == See Also ==