OpenDaylight JIRA https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 [OPNFLWPLUG-814] repetitive "Skip write statistics" WARN is flooding the karaf log https://jira.opendaylight.org/browse/OPNFLWPLUG-814 OpenFlowPlugin <p>Karaf log is fully with Repetative Warning below:</p> <p>2016-11-07 14:10:39,410 | WARN | entLoopGroup-9-5 | StatisticsGatheringUtils | 291 - org.opendaylight.openflowplugin.impl - 0.3.1.SNAPSHOT | Skip write statistics. Flow hash: -1483975337 not present in DeviceFlowRegistry</p> <p>Operating System: All<br/> Platform: All</p> OPNFLWPLUG-814 repetitive "Skip write statistics" WARN is flooding the karaf log Bug Resolved Done Unassigned zan cohen Mon, 7 Nov 2016 15:01:36 +0000 Mon, 27 Sep 2021 09:01:57 +0000 Sun, 11 Dec 2016 09:06:42 +0000 General 0 7 <p>debugging is too cumbersome with logs flooded like this. bumping importance to High/Major, if that's ok.</p> <p>It is caused by statistics arriving too fast, before flow is ever written to DeviceFlowRegistry. I think this WARN can be safely lowered to DEBUG, so it won't be flooding logs anymore.</p> <p>(In reply to Tomas Slusny from comment #2)<br/> &gt; It is caused by statistics arriving too fast, before flow is ever written to<br/> &gt; DeviceFlowRegistry. I think this WARN can be safely lowered to DEBUG, so it<br/> &gt; won't be flooding logs anymore.</p> <p>ok. if that's the case, here is a patch for it:<br/> <a href="https://git.opendaylight.org/gerrit/48183" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/48183</a></p> <p>sounds good....</p> <p><a href="https://git.opendaylight.org/gerrit/#/q/message:%22+lower+log+level+when+stats+come+before+flow+is+written+to+deviceflowregistry%22" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/q/message:%22+lower+log+level+when+stats+come+before+flow+is+written+to+deviceflowregistry%22</a></p> <p>Zan, looks like the log level change was merged. you can mark this resolved if you have time to double check it's working on your end.</p> Development External issue ID 7104 External issue URL Priority Rank 0|i033h3: