From 62bb392e9e8b31acabc55e27cf944635956f5dc7 Mon Sep 17 00:00:00 2001 From: Aaron Schulz Date: Sat, 2 Dec 2017 19:54:08 -0800 Subject: [PATCH] Lower DatabaseMysqlBase::lock logging to INFO Whether the lock() acquisition failing is a huge problem depends on what the caller is doing. Let the caller do any logging it needs. Bug: T180793 Change-Id: I3d05138d312d8b973df153bb511e69619d663c9d --- includes/libs/rdbms/database/DatabaseMysqlBase.php | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/includes/libs/rdbms/database/DatabaseMysqlBase.php b/includes/libs/rdbms/database/DatabaseMysqlBase.php index e0ff475959..305a056900 100644 --- a/includes/libs/rdbms/database/DatabaseMysqlBase.php +++ b/includes/libs/rdbms/database/DatabaseMysqlBase.php @@ -1044,7 +1044,7 @@ abstract class DatabaseMysqlBase extends Database { return true; } - $this->queryLogger->warning( __METHOD__ . " failed to acquire lock '{lockname}'", + $this->queryLogger->info( __METHOD__ . " failed to acquire lock '{lockname}'", [ 'lockname' => $lockName ] ); return false; -- 2.20.1