[NETCONF-100] Excessive amount of "Keepalive executor missing. ..." messages in logs when netconf devices miss "keepalive-executor" section in their configuration. Created: 24/Nov/15 Updated: 15/Mar/19 Resolved: 25/Nov/15 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Jozef Behran | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 4667 |
| Description |
|
The message from the "summary" occurs repeatedly when Lithium Stable is subjected to the scaling test (https://git.opendaylight.org/gerrit/#/c/28588/). The full line from the log file looks like this: 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 |
| Comments |
| Comment by Jozef Behran [ 24/Nov/15 ] |
|
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. |
| Comment by Tomas Cere [ 24/Nov/15 ] |
|
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. |
| Comment by Jozef Behran [ 25/Nov/15 ] |
|
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. 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. Also note that Beryllium does not exhibit this kind of problem (but 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 ... |
| Comment by Jozef Behran [ 25/Nov/15 ] |
|
Missing piece of comment: 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). |