aurora-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From s...@apache.org
Subject aurora git commit: Reduce log level of finding a valid leader
Date Fri, 01 Jul 2016 19:40:12 GMT
Repository: aurora
Updated Branches:
  refs/heads/master 205c308c5 -> 176c96a3f


Reduce log level of finding a valid leader

Since the introduction of the Curator-backend [1], we have been logging the currently active
leader on each request. This happens even if the queried scheduler is also the leading one.
By reducing the log level to debug, we can reduce the logging noise of Aurora significantly.

```
I0630 11:38:04.871 [qtp806277656-123, Slf4jRequestLog:60] 10.x.x.x - - [30/Jun/2016:11:38:04
+0000] "POST //master1.example.org/api HTTP/1.1" 307 0
I0630 11:38:04.879 [qtp806277656-129, LeaderRedirect:197] Found leader scheduler at [ServiceInstance(serviceEndpoint:Endpoint(host:master2.example.org,
port:8081), additionalEndpoints:{http=Endpoint(host:master2.example.org port:8081)}, status:ALIVE)]
I0630 11:38:04.879 [qtp806277656-129, LeaderRedirect:197] Found leader scheduler at [ServiceInstance(serviceEndpoint:Endpoint(host:master2.example.org,
port:8081), additionalEndpoints:{http=Endpoint(host:master2.example.org, port:8081)}, status:ALIVE)]
I0630 11:38:04.880 [qtp806277656-129, LeaderRedirect:197] Found leader scheduler at [ServiceInstance(serviceEndpoint:Endpoint(host:master2.example.org,
port:8081), additionalEndpoints:{http=Endpoint(host:master2.example.org, port:8081)}, status:ALIVE)]
```

[1] https://github.com/apache/aurora/commit/103dae6871eaa76914ab7fe17adaa174e93f537a#diff-1a20d033e88f293107537e09636007ffR190

Reviewed at https://reviews.apache.org/r/49527/


Project: http://git-wip-us.apache.org/repos/asf/aurora/repo
Commit: http://git-wip-us.apache.org/repos/asf/aurora/commit/176c96a3
Tree: http://git-wip-us.apache.org/repos/asf/aurora/tree/176c96a3
Diff: http://git-wip-us.apache.org/repos/asf/aurora/diff/176c96a3

Branch: refs/heads/master
Commit: 176c96a3f3b8ba276ad60a5c91492af048f792ef
Parents: 205c308
Author: Stephan Erb <serb@apache.org>
Authored: Fri Jul 1 21:39:46 2016 +0200
Committer: Stephan Erb <serb@apache.org>
Committed: Fri Jul 1 21:39:46 2016 +0200

----------------------------------------------------------------------
 src/main/java/org/apache/aurora/scheduler/http/LeaderRedirect.java | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/aurora/blob/176c96a3/src/main/java/org/apache/aurora/scheduler/http/LeaderRedirect.java
----------------------------------------------------------------------
diff --git a/src/main/java/org/apache/aurora/scheduler/http/LeaderRedirect.java b/src/main/java/org/apache/aurora/scheduler/http/LeaderRedirect.java
index 3847fb8..9bf6f52 100644
--- a/src/main/java/org/apache/aurora/scheduler/http/LeaderRedirect.java
+++ b/src/main/java/org/apache/aurora/scheduler/http/LeaderRedirect.java
@@ -194,7 +194,7 @@ class LeaderRedirect implements Closeable {
         LOG.warn("No serviceGroupMonitor in host set, will not redirect despite not being
leader.");
         return Optional.absent();
       case 1:
-        LOG.info("Found leader scheduler at " + hostSet);
+        LOG.debug("Found leader scheduler at " + hostSet);
         return Optional.of(Iterables.getOnlyElement(hostSet));
       default:
         LOG.error("Multiple serviceGroupMonitor detected, will not redirect: " + hostSet);


Mime
View raw message