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-100 netconf <p>The message from the "summary" occurs repeatedly when Lithium Stable is subjected to the scaling test (<a href="https://git.opendaylight.org/gerrit/#/c/28588/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/28588/</a>). The full line from the log file looks like this:</p> <p>2015-11-23 12:04:05,303 | WARN | entLoopGroup-2-2 | NetconfConnectorModule | 245 - org.opendaylight.controller.sal-netconf-connector - 1.2.3.SNAPSHOT | Keepalive executor missing. Using default instance for now, the configuration needs to be updated</p> <p>Operating System: All<br/> Platform: All</p> NETCONF-100

Excessive amount of "Keepalive executor missing. ..." messages in logs when netconf devices miss "keepalive-executor" section in their configuration.

Bug Resolved Won't Do Unassigned Jozef Behran Tue, 24 Nov 2015 14:40:29 +0000 Fri, 15 Mar 2019 22:22:17 +0000 Wed, 25 Nov 2015 17:54:04 +0000 netconf 0 1 <p>More information: A typical run of the aforementioned suite produces about 150 MB of these messages. They appear in bursts which are triggered by the Netconf devices being configured or deconfigured (or "connected or disconnected"? I can't tell for sure from the logs). The size of one of these bursts depends on the count of netconf devices in the configuration at the time the burst was triggered. It is roughly equal to twice of this count but sometimes there are a few more.</p> <p>This is just a warning for the user that the configuration is outdated and should have a section for keepalive-executor. It happens when a configuration is pushed and it is harmless and can be ignored.</p> <p>Ok, it turns out the warning itself is OK. Well, receiving one such warning for each device configuration that is missing the configuration section it warns about is okay. But receiving 147.5 MB of these warnings after the user configures 500 devices using such a configuration and then deconfigures them does not seem OK for me.</p> <p>And if I would try the 10000 devices, what I am going to get, 3 GB of logs (10000/500 = 20 and 147.5 MB * 20 = 2.95 GB)? Actually, I suspect that the amount of logs will be something like 60 GB because the more devices are in the configuration, the more warnings I will get for each configure/deconfigure operation.</p> <p>Also note that Beryllium does not exhibit this kind of problem (but</p> <p>Well, I found and added the missing piece of configuration, so this is no longer bugging me, therefore leaving as RESOLVED WONTFIX. But beware, this might bite somebody ...</p> <p>Missing piece of comment:</p> <p>Also note that Beryllium does not exhibit this kind of problem (but that might be due to the fact that the warning is at DEBUG level there).</p> Development External issue ID 4667 External issue URL ODL SR Target Milestone Rank 0|i01wgf: