From 33d60618482da197f69d53d0b3e059f9c10dfa90 Mon Sep 17 00:00:00 2001 From: Patrick Mueller Date: Wed, 1 Apr 2020 12:16:31 -0400 Subject: [PATCH] [Task Manager] Change info message "ran out Available Workers" to debug (#62083) (#62160) resolves https://github.com/elastic/kibana/issues/54920 The scenario this message warns about is actually something that we should expect to happen in a busy system - and we back off as we should. But there's no reason it needs to be info-logged, especially as it seems somewhat frightening. Changing to debug, so in case we do need this for diagnostic purposes, we can still get it via logging config. --- x-pack/plugins/task_manager/server/task_manager.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/x-pack/plugins/task_manager/server/task_manager.ts b/x-pack/plugins/task_manager/server/task_manager.ts index 641826de615b1b..c3f24a4aae88a5 100644 --- a/x-pack/plugins/task_manager/server/task_manager.ts +++ b/x-pack/plugins/task_manager/server/task_manager.ts @@ -411,7 +411,7 @@ export async function claimAvailableTasks( } } else { performance.mark('claimAvailableTasks.noAvailableWorkers'); - logger.info( + logger.debug( `[Task Ownership]: Task Manager has skipped Claiming Ownership of available tasks at it has ran out Available Workers.` ); }