Reduce logging in QuarantinedMonitorActor 85/33185/2
authorTom Pantelis <tpanteli@brocade.com>
Wed, 20 Jan 2016 19:01:41 +0000 (14:01 -0500)
committerGerrit Code Review <gerrit@opendaylight.org>
Thu, 21 Jan 2016 17:44:43 +0000 (17:44 +0000)
The QuarantinedMonitorActor logs every AssociationErrorEvent as warn
which causes a lot of output when a peer node is down as akka raises a
conneciton-refused event every 5 sec until it re-connects. Since we're
only interested in the specific quarantined event, which is logged at
warn, other events should log to debug to avoid the noise.

Change-Id: I26ab7db9a71d137ae3227409d6dcbf39675c6ec9
Signed-off-by: Tom Pantelis <tpanteli@brocade.com>
opendaylight/md-sal/sal-clustering-commons/src/main/java/org/opendaylight/controller/cluster/common/actor/QuarantinedMonitorActor.java

index 9d79e0f5e15114f299af815ba45cd11d14b62d90..8e2693e900dea8f2d0fa7bc1750eef126667d213 100644 (file)
@@ -70,7 +70,7 @@ public class QuarantinedMonitorActor extends UntypedActor {
                     LOG.debug("received AssociationErrorEvent, cause: InvalidAssociation", cause2);
                 }
             } else {
-                LOG.warn("received AssociationErrorEvent", cause);
+                LOG.debug("received AssociationErrorEvent", cause);
             }
         }
     }