From c02d1fb4c5aaa57f2c33e39dc4753b8111a62d53 Mon Sep 17 00:00:00 2001 From: Amir Sarabadani Date: Fri, 2 Dec 2016 14:12:40 +0330 Subject: [PATCH] slave -> replica in SessionConsistentConnectionManager Change-Id: Ie59c90fa5f4b18d4321f7924a4facd7ea9049f4a --- .../SessionConsistentConnectionManager.php | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/includes/libs/rdbms/connectionmanager/SessionConsistentConnectionManager.php b/includes/libs/rdbms/connectionmanager/SessionConsistentConnectionManager.php index e183823244..fb031822e7 100644 --- a/includes/libs/rdbms/connectionmanager/SessionConsistentConnectionManager.php +++ b/includes/libs/rdbms/connectionmanager/SessionConsistentConnectionManager.php @@ -8,14 +8,14 @@ use DBConnRef; /** * Database connection manager. * - * This manages access to master and slave databases. It also manages state that indicates whether - * the slave databases are possibly outdated after a write operation, and thus the master database + * This manages access to master and replica databases. It also manages state that indicates whether + * the replica databases are possibly outdated after a write operation, and thus the master database * should be used for subsequent read operations. * * @note: Services that access overlapping sets of database tables, or interact with logically * related sets of data in the database, should share a SessionConsistentConnectionManager. * Services accessing unrelated sets of information may prefer to not share a - * SessionConsistentConnectionManager, so they can still perform read operations against slave + * SessionConsistentConnectionManager, so they can still perform read operations against replica * databases after a (unrelated, per the assumption) write operation to the master database. * Generally, sharing a SessionConsistentConnectionManager improves consistency (by avoiding race * conditions due to replication lag), but can reduce performance (by directing more read -- 2.20.1