Onder Kalaci 7b4eb9611b Properly terminate connections at the end session ... Citus coordinator (or MX nodes) caches `citus.max_cached_conns_per_worker` connections per node. This means that, those connections are not terminated after each statement. Instead, cached to avoid the cost of re-establishment. This is crucial for OLTP performance. The problem with that approach is that, we never properly handle the termnation of those cached connections. For instance, when a session on the coordinator disconnects, you'd see the following logs on the workers: ``` 2020-03-20 09:13:39.454 CET [64028] LOG: could not receive data from client: Connection reset by peer ``` With this patch, we're terminating the cached connections properly at the end of the connection.		2020-03-20 17:34:34 +01:00
..
distributed	Properly terminate connections at the end session	2020-03-20 17:34:34 +01:00
.gitignore	Initial commit of Citus 5.0	2016-02-11 04:05:32 +02:00