Skip to content
Permalink
Browse files
QueryScheduler: Log per-query message at DEBUG level. (#12467)
We generally want to avoid having any routine per-query messages at
INFO level, because they pollute logs.
  • Loading branch information
gianm committed Apr 22, 2022
1 parent 63a993c commit b7621226d28493899c1331f7bf45469706c248c5
Showing 1 changed file with 6 additions and 1 deletion.
@@ -159,7 +159,12 @@ public <T> Query<T> prioritizeAndLaneQuery(QueryPlus<T> queryPlus, Set<SegmentSe
Optional<Integer> priority = prioritizationStrategy.computePriority(queryPlus, segments);
query = priority.map(query::withPriority).orElse(query);
Optional<String> lane = laningStrategy.computeLane(queryPlus.withQuery(query), segments);
LOGGER.info("[%s] lane assigned to [%s] query with [%,d] priority", lane.orElse("default"), query.getType(), priority.orElse(Integer.valueOf(0)));
LOGGER.debug(
"[%s] lane assigned to [%s] query with [%,d] priority",
lane.orElse("default"),
query.getType(),
priority.orElse(0)
);
final ServiceMetricEvent.Builder builderUsr = ServiceMetricEvent.builder().setFeed("metrics")
.setDimension("lane", lane.orElse("default"))
.setDimension("dataSource", query.getDataSource().getTableNames())

0 comments on commit b762122

Please sign in to comment.