Changes between Version 11 and Version 12 of InstallationGuidelines/Cluster
- Timestamp:
- 11/30/17 11:48:47 (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
InstallationGuidelines/Cluster
v11 v12 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. 65 65 === Solution === 66 The solution is to set a much shorter tcp_keepalives_idle in postgresql.conf, 67 i.e. shorter than the router timeout - then the router won't drop the 68 connections even if the worker never does anything, and libpq will never get 69 stuck. 66 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. 70 67 71 68 == See Also ==