From 8ad0394d698530e90e4e47d6d34ab58cd4e98b26 Mon Sep 17 00:00:00 2001 From: Aaron Schulz Date: Mon, 15 Aug 2016 14:29:04 -0700 Subject: [PATCH] Fix DBLockManager comments Change-Id: I5431caf4b80995c71d4bc5ab739954d70081111a --- includes/filebackend/lockmanager/DBLockManager.php | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/includes/filebackend/lockmanager/DBLockManager.php b/includes/filebackend/lockmanager/DBLockManager.php index b61b08dd11..c9aad43a48 100644 --- a/includes/filebackend/lockmanager/DBLockManager.php +++ b/includes/filebackend/lockmanager/DBLockManager.php @@ -26,9 +26,8 @@ * * This is meant for multi-wiki systems that may share files. * - * All lock requests for a resource, identified by a hash string, will map - * to one bucket. Each bucket maps to one or several peer DBs, each on their - * own server, all having the filelocks.sql tables (with row-level locking). + * All lock requests for a resource, identified by a hash string, will map to one bucket. + * Each bucket maps to one or several peer DBs, each on their own server. * A majority of peer DBs must agree for a lock to be acquired. * * Caching is used to avoid hitting servers that are down. @@ -243,6 +242,8 @@ abstract class DBLockManager extends QuorumLockManager { /** * MySQL version of DBLockManager that supports shared locks. + * + * All lock servers must have the innodb table defined in locking/filelocks.sql. * All locks are non-blocking, which avoids deadlocks. * * @ingroup LockManager -- 2.20.1