Added more logging to the scheduler library.

Trivial change involving adding more logging to the scheduler library
while sending/receiving events.

Review: https://reviews.apache.org/r/37510


Project: http://git-wip-us.apache.org/repos/asf/mesos/repo
Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/5ce84492
Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/5ce84492
Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/5ce84492

Branch: refs/heads/master
Commit: 5ce844922b79bc7cf29d0bb0d01e031470f38c59
Parents: 4588f5a
Author: Anand Mazumdar <[email protected]>
Authored: Sun Aug 16 15:46:57 2015 -0700
Committer: Vinod Kone <[email protected]>
Committed: Sun Aug 16 15:46:57 2015 -0700

----------------------------------------------------------------------
 src/scheduler/scheduler.cpp | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/mesos/blob/5ce84492/src/scheduler/scheduler.cpp
----------------------------------------------------------------------
diff --git a/src/scheduler/scheduler.cpp b/src/scheduler/scheduler.cpp
index 0aef68e..d3d6682 100644
--- a/src/scheduler/scheduler.cpp
+++ b/src/scheduler/scheduler.cpp
@@ -300,6 +300,8 @@ protected:
       return Nothing();
     }
 
+    VLOG(1) << "Sending " << call.type() << " call to " << master.get();
+
     // TODO(vinod): Add support for sending MESSAGE calls directly
     // to the slave, instead of relaying it through the master, as
     // the scheduler driver does.
@@ -447,8 +449,10 @@ protected:
     }
 
     if (isLocallyInjected) {
-      VLOG(1) << "Enqueuing locally injected event "
-              << stringify(event.type());
+      VLOG(1) << "Enqueuing locally injected event " << 
stringify(event.type());
+    } else {
+      VLOG(1) << "Enqueuing event " << stringify(event.type()) << " received"
+              << " from " << master.get();
     }
 
     // Queue up the event and invoke the 'received' callback if this

Reply via email to