Logs being spammed with org.opendaylight.openflowplugin.impl - 0.8.0 | Switch Idle state occurred, node=/10.30.170.99:44168|auxId=0

Description

in a ~2.5h CSIT job, the below message is seen 1600+ times.

47217:2018-12-10T17:22:00,630 | INFO  | ofppool-15       | SystemNotificationsListenerImpl  | 386 - org.opendaylight.openflowplugin.impl - 0.8.0 | Switch Idle state occurred, node=/10.30.170.99:44168|auxId=0

if the root cause event is expected and happening reasonably 1600+ times needs to be
understood first. If so, we should remove that log entirely or lower it's level to DEBUG or
higher so that it's not spamming a production environment with duplicate messages.

Unless I'm not seeing the true value in the message.

Environment

None

Activity

Show:

Arunprakash D February 6, 2019 at 6:56 AM

@Shweta Chaturvedi will raise a review to move this message from INFO to DEBUG.

JamO Luhrsen December 19, 2018 at 5:02 PM

Apologies for not including a log. Here is a karaf log

but, no I don't see exceptions immediately after this log statement.

I'm wondering if this is related to OPENFLWPLUG-1053 / 1057?

Arunprakash D December 19, 2018 at 7:02 AM

@JamO Luhrsen, is there exceptions like "Exception while waiting for echoReply from" immediately after the log you have seen?

When the netty channel is idle for more than 15sec, SwitchIdleEvent will be generated and openflowplugin will print the info log "Switch Idle state occurred" and sends a echo message to the switch and if it didn't get reply within next 2 sec, the switch will be disconnected. If it gets reply with in 2 sec, it will continue to maintain the tcp connection.

When openflowplugin actually disconnects the switch, it will print "Exception while waiting for echoReply from". If this exception is not observed, then only the switch idle state is occuring in the setup.