https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/NETCONF-1167 netconf <p>NETCONF devices configured but unreachable may cause performance issues in other connected NETCONF sessions or even cause disconnection of the sessions.</p> <p>AsyncSshHandler has <a href="https://github.com/opendaylight/netconf/blob/master/netconf/netconf-netty-util/src/main/java/org/opendaylight/netconf/nettyutil/handler/ssh/client/AsyncSshHandler.java#L154" class="external-link" target="_blank" rel="nofollow noopener">a blocking call</a> to verify SSH session connection and this means that the thread is occupied for the timeout period if the device is unreachable. The default values of <tt>between-attempts-timeout-millis</tt> and <tt>connection-timeout-millis</tt> are <tt>2000</tt> (2 seconds) and <tt>20000</tt> (20 seconds), respectively, so assuming <tt>sleep-factor</tt> is <tt>1.0</tt> (the interval between connection attempts stays the same), a single unreachable device can take up about 0.9 CPU core. So a relatively small number of unreachable devices can easily overwhelm the whole thread pool available to all the NETCONF sessions and even the NETCONF sessions without such connectivity issue can experience performance issue - long latency in the RPC response and in some cases it may be hard to maintain connectivity depending on the keepalive settings in the device.</p> NETCONF-1167

Slow NETCONF RPC response caused by unreachable devices

Bug Medium Resolved Done Peter Suna Sangwook Ha pt Tue, 26 Sep 2023 00:11:10 +0000 Wed, 10 Jan 2024 13:05:16 +0000 Wed, 10 Jan 2024 13:05:16 +0000 5.0.7 4.0.8 6.0.4 5.0.10 6.0.6 netconf 0 2 <p>This issue is present until branch 6.0.x. The master branch is not affected.</p> <p>Steps to reproduce:</p> <ol> <li>Start Karaf: <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>feature:install odl-restconf-all odl-netconf-topology </pre> </div></div></li> <li>Drop ports for test devices: <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>sudo iptables -I INPUT -p tcp --dport 17840 -j DROP sudo iptables -I INPUT -p tcp --dport 17841 -j DROP sudo iptables -I INPUT -p tcp --dport 17842 -j DROP sudo iptables -I INPUT -p tcp --dport 17843 -j DROP sudo iptables -I INPUT -p tcp --dport 17844 -j DROP sudo iptables -I INPUT -p tcp --dport 17845 -j DROP sudo iptables -I INPUT -p tcp --dport 17846 -j DROP </pre> </div></div></li> </ol> <ol> <li>Start 20 devices <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>java -jar netconf-testtool-6.0.6-SNAPSHOT-executable.jar --device-count 20 --ssh true --md-sal true --controller-ip 127.0.0.1 --controller-port 8181 </pre> </div></div></li> </ol> <ol> <li>Get all devices <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>curl 'http://192.168.56.100:8181/rests/data/network-topology:network-topology/topology=topology-netconf' \ --header 'Authorization: Basic YWRtaW46YWRtaW4=' </pre> </div></div></li> </ol> <p>In all devices, there is at least one device that is not immediately connected, and its ports were not set to drop all packets. These devices connect after some time.</p> Development Rank 0|i046lr: