<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Le 05/03/2019 à 13:22, Steve Singer a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:alpine.DEB.2.11.1903050712590.22502@opti.atlantida">On
Tue, 5 Mar 2019, SAS wrote:
<br>
<br>
<blockquote type="cite">Thank you for your answer.
<br>
<br>
I could easily drop some paths, and then lower the number of
established connections on some
<br>
nodes.
<br>
<br>
Could you point me to what has changed between 2.1 and 2.2
branches that causes this connections
<br>
increase? The paths were there before the upgrade.
<br>
</blockquote>
<br>
It has to do with the changes to how DDL is handled.
<br>
In 2.1 and earlier DDL was treated as a special type of event and
was replicated by this event in sl_event. There were cases where
DDL and data could be replicated in the wrong order.
<br>
<br>
In 2.2 there is now a table specifically for DDL changes, like
sl_log. The DDL from this table is pulled in the correct order by
the listener threads through the listener connection.
<br>
<br>
DDL can be submitted on any node, and for nodes that aren't
providing a subscription there isn't a clear cascaded network
route though other nodes.
<br>
<br>
For larger node setups it might be nice to have a way of
designating nodes as 'edge only' nodes, where they can't be
origin's, providers or failover targets and they can't accept DDL
submissions. These nodes wouldn't have to generate any events and
so other nodes wouldn't have to listen for their events. We don't
currently support this though.
<br>
<br>
Hope that helps.
<br>
</blockquote>
<p>Thank you, I now have a better understanding of the situation.</p>
<p><br>
</p>
<div class="moz-signature">-- <br>
<div>
<div><font color="#00aee6">Dr Stéphane Schildknecht</font></div>
<div>Contact régional PostgreSQL pour l'Europe francophone</div>
<div>+33 617 11 37 42</div>
<br>
</div>
</div>
</body>
</html>