MediaWiki REL1_28
RedisLockManager.php
Go to the documentation of this file.
1<?php
42 protected $lockTypeMap = [
43 self::LOCK_SH => self::LOCK_SH,
44 self::LOCK_UW => self::LOCK_SH,
45 self::LOCK_EX => self::LOCK_EX
46 ];
47
49 protected $redisPool;
50
52 protected $lockServers = [];
53
64 public function __construct( array $config ) {
65 parent::__construct( $config );
66
67 $this->lockServers = $config['lockServers'];
68 // Sanitize srvsByBucket config to prevent PHP errors
69 $this->srvsByBucket = array_filter( $config['srvsByBucket'], 'is_array' );
70 $this->srvsByBucket = array_values( $this->srvsByBucket ); // consecutive
71
72 $config['redisConfig']['serializer'] = 'none';
73 $this->redisPool = RedisConnectionPool::singleton( $config['redisConfig'] );
74 }
75
76 protected function getLocksOnServer( $lockSrv, array $pathsByType ) {
77 $status = StatusValue::newGood();
78
79 $pathList = call_user_func_array( 'array_merge', array_values( $pathsByType ) );
80
81 $server = $this->lockServers[$lockSrv];
82 $conn = $this->redisPool->getConnection( $server, $this->logger );
83 if ( !$conn ) {
84 foreach ( $pathList as $path ) {
85 $status->fatal( 'lockmanager-fail-acquirelock', $path );
86 }
87
88 return $status;
89 }
90
91 $pathsByKey = []; // (type:hash => path) map
92 foreach ( $pathsByType as $type => $paths ) {
93 $typeString = ( $type == LockManager::LOCK_SH ) ? 'SH' : 'EX';
94 foreach ( $paths as $path ) {
95 $pathsByKey[$this->recordKeyForPath( $path, $typeString )] = $path;
96 }
97 }
98
99 try {
100 static $script =
102<<<LUA
103 local failed = {}
104 -- Load input params (e.g. session, ttl, time of request)
105 local rSession, rTTL, rMaxTTL, rTime = unpack(ARGV)
106 -- Check that all the locks can be acquired
107 for i,requestKey in ipairs(KEYS) do
108 local _, _, rType, resourceKey = string.find(requestKey,"(%w+):(%w+)$")
109 local keyIsFree = true
110 local currentLocks = redis.call('hKeys',resourceKey)
111 for i,lockKey in ipairs(currentLocks) do
112 -- Get the type and session of this lock
113 local _, _, type, session = string.find(lockKey,"(%w+):(%w+)")
114 -- Check any locks that are not owned by this session
115 if session ~= rSession then
116 local lockExpiry = redis.call('hGet',resourceKey,lockKey)
117 if 1*lockExpiry < 1*rTime then
118 -- Lock is stale, so just prune it out
119 redis.call('hDel',resourceKey,lockKey)
120 elseif rType == 'EX' or type == 'EX' then
121 keyIsFree = false
122 break
123 end
124 end
125 end
126 if not keyIsFree then
127 failed[#failed+1] = requestKey
128 end
129 end
130 -- If all locks could be acquired, then do so
131 if #failed == 0 then
132 for i,requestKey in ipairs(KEYS) do
133 local _, _, rType, resourceKey = string.find(requestKey,"(%w+):(%w+)$")
134 redis.call('hSet',resourceKey,rType .. ':' .. rSession,rTime + rTTL)
135 -- In addition to invalidation logic, be sure to garbage collect
136 redis.call('expire',resourceKey,rMaxTTL)
137 end
138 end
139 return failed
140LUA;
141 $res = $conn->luaEval( $script,
142 array_merge(
143 array_keys( $pathsByKey ), // KEYS[0], KEYS[1],...,KEYS[N]
144 [
145 $this->session, // ARGV[1]
146 $this->lockTTL, // ARGV[2]
147 self::MAX_LOCK_TTL, // ARGV[3]
148 time() // ARGV[4]
149 ]
150 ),
151 count( $pathsByKey ) # number of first argument(s) that are keys
152 );
153 } catch ( RedisException $e ) {
154 $res = false;
155 $this->redisPool->handleError( $conn, $e );
156 }
157
158 if ( $res === false ) {
159 foreach ( $pathList as $path ) {
160 $status->fatal( 'lockmanager-fail-acquirelock', $path );
161 }
162 } else {
163 foreach ( $res as $key ) {
164 $status->fatal( 'lockmanager-fail-acquirelock', $pathsByKey[$key] );
165 }
166 }
167
168 return $status;
169 }
170
171 protected function freeLocksOnServer( $lockSrv, array $pathsByType ) {
172 $status = StatusValue::newGood();
173
174 $pathList = call_user_func_array( 'array_merge', array_values( $pathsByType ) );
175
176 $server = $this->lockServers[$lockSrv];
177 $conn = $this->redisPool->getConnection( $server, $this->logger );
178 if ( !$conn ) {
179 foreach ( $pathList as $path ) {
180 $status->fatal( 'lockmanager-fail-releaselock', $path );
181 }
182
183 return $status;
184 }
185
186 $pathsByKey = []; // (type:hash => path) map
187 foreach ( $pathsByType as $type => $paths ) {
188 $typeString = ( $type == LockManager::LOCK_SH ) ? 'SH' : 'EX';
189 foreach ( $paths as $path ) {
190 $pathsByKey[$this->recordKeyForPath( $path, $typeString )] = $path;
191 }
192 }
193
194 try {
195 static $script =
197<<<LUA
198 local failed = {}
199 -- Load input params (e.g. session)
200 local rSession = unpack(ARGV)
201 for i,requestKey in ipairs(KEYS) do
202 local _, _, rType, resourceKey = string.find(requestKey,"(%w+):(%w+)$")
203 local released = redis.call('hDel',resourceKey,rType .. ':' .. rSession)
204 if released > 0 then
205 -- Remove the whole structure if it is now empty
206 if redis.call('hLen',resourceKey) == 0 then
207 redis.call('del',resourceKey)
208 end
209 else
210 failed[#failed+1] = requestKey
211 end
212 end
213 return failed
214LUA;
215 $res = $conn->luaEval( $script,
216 array_merge(
217 array_keys( $pathsByKey ), // KEYS[0], KEYS[1],...,KEYS[N]
218 [
219 $this->session, // ARGV[1]
220 ]
221 ),
222 count( $pathsByKey ) # number of first argument(s) that are keys
223 );
224 } catch ( RedisException $e ) {
225 $res = false;
226 $this->redisPool->handleError( $conn, $e );
227 }
228
229 if ( $res === false ) {
230 foreach ( $pathList as $path ) {
231 $status->fatal( 'lockmanager-fail-releaselock', $path );
232 }
233 } else {
234 foreach ( $res as $key ) {
235 $status->fatal( 'lockmanager-fail-releaselock', $pathsByKey[$key] );
236 }
237 }
238
239 return $status;
240 }
241
242 protected function releaseAllLocks() {
243 return StatusValue::newGood(); // not supported
244 }
245
246 protected function isServerUp( $lockSrv ) {
247 $conn = $this->redisPool->getConnection( $this->lockServers[$lockSrv], $this->logger );
248
249 return (bool)$conn;
250 }
251
257 protected function recordKeyForPath( $path, $type ) {
258 return implode( ':',
259 [ __CLASS__, 'locks', "$type:" . $this->sha1Base36Absolute( $path ) ] );
260 }
261
265 function __destruct() {
266 while ( count( $this->locksHeld ) ) {
267 $pathsByType = [];
268 foreach ( $this->locksHeld as $path => $locks ) {
269 foreach ( $locks as $type => $count ) {
270 $pathsByType[$type][] = $path;
271 }
272 }
273 $this->unlockByType( $pathsByType );
274 }
275 }
276}
Apache License January AND DISTRIBUTION Definitions License shall mean the terms and conditions for and distribution as defined by Sections through of this document Licensor shall mean the copyright owner or entity authorized by the copyright owner that is granting the License Legal Entity shall mean the union of the acting entity and all other entities that control are controlled by or are under common control with that entity For the purposes of this definition control direct or to cause the direction or management of such whether by contract or including but not limited to software source documentation and configuration files Object form shall mean any form resulting from mechanical transformation or translation of a Source including but not limited to compiled object generated and conversions to other media types Work shall mean the work of whether in Source or Object made available under the as indicated by a copyright notice that is included in or attached to the whether in Source or Object that is based or other modifications as a whole
and(b) You must cause any modified files to carry prominent notices stating that You changed the files
Apache License January AND DISTRIBUTION Definitions License shall mean the terms and conditions for and distribution as defined by Sections through of this document Licensor shall mean the copyright owner or entity authorized by the copyright owner that is granting the License Legal Entity shall mean the union of the acting entity and all other entities that control are controlled by or are under common control with that entity For the purposes of this definition control direct or to cause the direction or management of such whether by contract or including but not limited to software source documentation and configuration files Object form shall mean any form resulting from mechanical transformation or translation of a Source including but not limited to compiled object generated and conversions to other media types Work shall mean the work of whether in Source or Object made available under the as indicated by a copyright notice that is included in or attached to the whether in Source or Object that is based or other modifications as a an original work of authorship For the purposes of this Derivative Works shall not include works that remain separable or merely the Work and Derivative Works thereof Contribution shall mean any work of including the original version of the Work and any modifications or additions to that Work or Derivative Works that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner For the purposes of this submitted means any form of or written communication sent to the Licensor or its including but not limited to communication on electronic mailing source code control and issue tracking systems that are managed by
lock(array $paths, $type=self::LOCK_EX, $timeout=0)
Lock the resources at the given abstract paths.
const LOCK_SH
Lock types; stronger locks have higher values.
sha1Base36Absolute( $path)
Get the base 36 SHA-1 of a string, padded to 31 digits.
unlockByType(array $pathsByType)
Unlock the resources at the given abstract paths.
Version of LockManager that uses a quorum from peer servers for locks.
Helper class to manage Redis connections.
static singleton(array $options)
Manage locks using redis servers.
__construct(array $config)
Construct a new instance from configuration.
recordKeyForPath( $path, $type)
freeLocksOnServer( $lockSrv, array $pathsByType)
Get a connection to a lock server and release locks on $paths.
RedisConnectionPool $redisPool
getLocksOnServer( $lockSrv, array $pathsByType)
Get a connection to a lock server and acquire locks.
array $lockServers
Map server names to hostname/IP and port numbers.
releaseAllLocks()
Release all locks that this session is holding.
__destruct()
Make sure remaining locks get cleared for sanity.
array $lockTypeMap
Mapping of lock types to the type actually used.
isServerUp( $lockSrv)
Check if a lock server is up.
=Architecture==Two class hierarchies are used to provide the functionality associated with the different content models:*Content interface(and AbstractContent base class) define functionality that acts on the concrete content of a page, and *ContentHandler base class provides functionality specific to a content model, but not acting on concrete content. The most important function of ContentHandler is to act as a factory for the appropriate implementation of Content. These Content objects are to be used by MediaWiki everywhere, instead of passing page content around as text. All manipulation and analysis of page content must be done via the appropriate methods of the Content object. For each content model, a subclass of ContentHandler has to be registered with $wgContentHandlers. The ContentHandler object for a given content model can be obtained using ContentHandler::getForModelID($id). Also Title, WikiPage and Revision now have getContentHandler() methods for convenience. ContentHandler objects are singletons that provide functionality specific to the content type, but not directly acting on the content of some page. ContentHandler::makeEmptyContent() and ContentHandler::unserializeContent() can be used to create a Content object of the appropriate type. However, it is recommended to instead use WikiPage::getContent() resp. Revision::getContent() to get a page 's content as a Content object. These two methods should be the ONLY way in which page content is accessed. Another important function of ContentHandler objects is to define custom action handlers for a content model, see ContentHandler::getActionOverrides(). This is similar to what WikiPage::getActionOverrides() was already doing.==Serialization==With the ContentHandler facility, page content no longer has to be text based. Objects implementing the Content interface are used to represent and handle the content internally. For storage and data exchange, each content model supports at least one serialization format via ContentHandler::serializeContent($content). The list of supported formats for a given content model can be accessed using ContentHandler::getSupportedFormats(). Content serialization formats are identified using MIME type like strings. The following formats are built in:*text/x-wiki - wikitext *text/javascript - for js pages *text/css - for css pages *text/plain - for future use, e.g. with plain text messages. *text/html - for future use, e.g. with plain html messages. *application/vnd.php.serialized - for future use with the api and for extensions *application/json - for future use with the api, and for use by extensions *application/xml - for future use with the api, and for use by extensions In PHP, use the corresponding CONTENT_FORMAT_XXX constant. Note that when using the API to access page content, especially action=edit, action=parse and action=query &prop=revisions, the model and format of the content should always be handled explicitly. Without that information, interpretation of the provided content is not reliable. The same applies to XML dumps generated via maintenance/dumpBackup.php or Special:Export. Also note that the API will provide encapsulated, serialized content - so if the API was called with format=json, and contentformat is also json(or rather, application/json), the page content is represented as a string containing an escaped json structure. Extensions that use JSON to serialize some types of page content may provide specialized API modules that allow access to that content in a more natural form.==Compatibility==The ContentHandler facility is introduced in a way that should allow all existing code to keep functioning at least for pages that contain wikitext or other text based content. However, a number of functions and hooks have been deprecated in favor of new versions that are aware of the page 's content model, and will now generate warnings when used. Most importantly, the following functions have been deprecated:*Revisions::getText() is deprecated in favor Revisions::getContent() *WikiPage::getText() is deprecated in favor WikiPage::getContent() Also, the old Article::getContent()(which returns text) is superceded by Article::getContentObject(). However, both methods should be avoided since they do not provide clean access to the page 's actual content. For instance, they may return a system message for non-existing pages. Use WikiPage::getContent() instead. Code that relies on a textual representation of the page content should eventually be rewritten. However, ContentHandler::getContentText() provides a stop-gap that can be used to get text for a page. Its behavior is controlled by $wgContentHandlerTextFallback it
The ContentHandler facility adds support for arbitrary content types on wiki instead of relying on wikitext for everything It was introduced in MediaWiki Each kind of and so on Built in content types are
$res
Definition database.txt:21
We use the convention $dbr for read and $dbw for write to help you keep track of whether the database object is a the world will explode Or to be a subsequent write query which succeeded on the master may fail when replicated to the slave due to a unique key collision Replication on the slave will stop and it may take hours to repair the database and get it back online Setting read_only in my cnf on the slave will avoid this but given the dire we prefer to have as many checks as possible We provide a but the wrapper functions like please read the documentation for except in special pages derived from QueryPage It s a common pitfall for new developers to submit code containing SQL queries which examine huge numbers of rows Remember that COUNT * is(N), counting rows in atable is like counting beans in a bucket.------------------------------------------------------------------------ Replication------------------------------------------------------------------------The largest installation of MediaWiki, Wikimedia, uses a large set ofslave MySQL servers replicating writes made to a master MySQL server. Itis important to understand the issues associated with this setup if youwant to write code destined for Wikipedia.It 's often the case that the best algorithm to use for a given taskdepends on whether or not replication is in use. Due to our unabashedWikipedia-centrism, we often just use the replication-friendly version, but if you like, you can use wfGetLB() ->getServerCount() > 1 tocheck to see if replication is in use.===Lag===Lag primarily occurs when large write queries are sent to the master.Writes on the master are executed in parallel, but they are executed inserial when they are replicated to the slaves. The master writes thequery to the binlog when the transaction is committed. The slaves pollthe binlog and start executing the query as soon as it appears. They canservice reads while they are performing a write query, but will not readanything more from the binlog and thus will perform no more writes. Thismeans that if the write query runs for a long time, the slaves will lagbehind the master for the time it takes for the write query to complete.Lag can be exacerbated by high read load. MediaWiki 's load balancer willstop sending reads to a slave when it is lagged by more than 30 seconds.If the load ratios are set incorrectly, or if there is too much loadgenerally, this may lead to a slave permanently hovering around 30seconds lag.If all slaves are lagged by more than 30 seconds, MediaWiki will stopwriting to the database. All edits and other write operations will berefused, with an error returned to the user. This gives the slaves achance to catch up. Before we had this mechanism, the slaves wouldregularly lag by several minutes, making review of recent editsdifficult.In addition to this, MediaWiki attempts to ensure that the user seesevents occurring on the wiki in chronological order. A few seconds of lagcan be tolerated, as long as the user sees a consistent picture fromsubsequent requests. This is done by saving the master binlog positionin the session, and then at the start of each request, waiting for theslave to catch up to that position before doing any reads from it. Ifthis wait times out, reads are allowed anyway, but the request isconsidered to be in "lagged slave mode". Lagged slave mode can bechecked by calling wfGetLB() ->getLaggedSlaveMode(). The onlypractical consequence at present is a warning displayed in the pagefooter.===Lag avoidance===To avoid excessive lag, queries which write large numbers of rows shouldbe split up, generally to write one row at a time. Multi-row INSERT ...SELECT queries are the worst offenders should be avoided altogether.Instead do the select first and then the insert.===Working with lag===Despite our best efforts, it 's not practical to guarantee a low-lagenvironment. Lag will usually be less than one second, but mayoccasionally be up to 30 seconds. For scalability, it 's very importantto keep load on the master low, so simply sending all your queries tothe master is not the answer. So when you have a genuine need forup-to-date data, the following approach is advised:1) Do a quick query to the master for a sequence number or timestamp 2) Run the full query on the slave and check if it matches the data you gotfrom the master 3) If it doesn 't, run the full query on the masterTo avoid swamping the master every time the slaves lag, use of thisapproach should be kept to a minimum. In most cases you should just readfrom the slave and let the user deal with the delay.------------------------------------------------------------------------ Lock contention------------------------------------------------------------------------Due to the high write rate on Wikipedia(and some other wikis), MediaWiki developers need to be very careful to structure their writesto avoid long-lasting locks. By default, MediaWiki opens a transactionat the first query, and commits it before the output is sent. Locks willbe held from the time when the query is done until the commit. So youcan reduce lock time by doing as much processing as possible before youdo your write queries.Often this approach is not good enough, and it becomes necessary toenclose small groups of queries in their own transaction. Use thefollowing syntax:$dbw=wfGetDB(DB_MASTER
deferred txt A few of the database updates required by various functions here can be deferred until after the result page is displayed to the user For updating the view updating the linked to tables after a etc PHP does not yet have any way to tell the server to actually return and disconnect while still running these but it might have such a feature in the future We handle these by creating a deferred update object and putting those objects on a global then executing the whole list after the page is displayed We don t do anything smart like collating updates to the same table or such because the list is almost always going to have just one item on if that
Definition deferred.txt:13
This document is intended to provide useful advice for parties seeking to redistribute MediaWiki to end users It s targeted particularly at maintainers for Linux since it s been observed that distribution packages of MediaWiki often break We ve consistently had to recommend that users seeking support use official tarballs instead of their distribution s and this often solves whatever problem the user is having It would be nice if this could such as
globals txt Globals are evil The original MediaWiki code relied on globals for processing context far too often MediaWiki development since then has been a story of slowly moving context out of global variables and into objects Storing processing context in object member variables allows those objects to be reused in a much more flexible way Consider the elegance of
database rows
Definition globals.txt:10
this hook is for auditing only RecentChangesLinked and Watchlist RecentChangesLinked and Watchlist e g Watchlist removed from all revisions and log entries to which it was applied This gives extensions a chance to take it off their books as the deletion has already been partly carried out by this point or something similar the user will be unable to create the tag set $status
Definition hooks.txt:1049
the array() calling protocol came about after MediaWiki 1.4rc1.
in this case you re responsible for computing and outputting the entire conflict i e
Definition hooks.txt:1379
namespace are movable Hooks may change this value to override the return value of MWNamespace::isMovable(). 'NewDifferenceEngine' do that in ParserLimitReportFormat instead use this to modify the parameters of the image and a DIV can begin in one section and end in another Make sure your code can handle that case gracefully See the EditSectionClearerLink extension for an example zero but section is usually empty its values are the globals values before the output is cached one of or reset my talk my contributions etc etc otherwise the built in rate limiting checks are if enabled allows for interception of redirect as a string mapping parameter names to values & $type
Definition hooks.txt:2568
We ve cleaned up the code here by removing clumps of infrequently used code and moving them off somewhere else It s much easier for someone working with this code to see what s _really_ going and make changes or fix bugs In addition
Definition hooks.txt:90
null for the local wiki Added in
Definition hooks.txt:1558
returning false will NOT prevent logging a wrapping ErrorException instead of letting the login form give the generic error message that the account does not exist For when the account has been renamed or deleted or an array to pass a message key and parameters create2 Corresponds to logging log_action database field and which is displayed in the UI similar to $comment this hook should only be used to add variables that depend on the current page request
Definition hooks.txt:2158
this hook is for auditing only RecentChangesLinked and Watchlist RecentChangesLinked and Watchlist e g Watchlist removed from all revisions and log entries to which it was applied This gives extensions a chance to take it off their books as the deletion has already been partly carried out by this point or something similar the user will be unable to create the tag set and then return false from the hook function Ensure you consume the ChangeTagAfterDelete hook to carry out custom deletion actions as context called by AbstractContent::getParserOutput May be used to override the normal model specific rendering of page content as context as context the output can only depend on parameters provided to this hook not on global state indicating whether full HTML should be generated If generation of HTML may be but other information should still be present in the ParserOutput object to manipulate or replace but no entry for that model exists in $wgContentHandlers if desired whether it is OK to use $contentModel on $title Handler functions that modify $ok should generally return false to prevent further hooks from further modifying $ok inclusive false for true for descending in case the handler function wants to provide a converted Content object Note that $result getContentModel() must return $toModel. 'CustomEditor' $rcid is used in generating this variable which contains information about the new such as the revision s whether the revision was marked as a minor edit or not
Definition hooks.txt:1207
returning false will NOT prevent logging $e
Definition hooks.txt:2110
as see the revision history and available at free of to any person obtaining a copy of this software and associated documentation to deal in the Software without including without limitation the rights to and or sell copies of the and to permit persons to whom the Software is furnished to do so
Definition LICENSE.txt:13
injection txt This is an overview of how MediaWiki makes use of dependency injection The design described here grew from the discussion of RFC T384 The term dependency this means that anything an object needs to operate should be injected from the the object itself should only know narrow no concrete implementation of the logic it relies on The requirement to inject everything typically results in an architecture that based on two main types of and essentially stateless service objects that use other service objects to operate on the value objects As of the beginning MediaWiki is only starting to use the DI approach Much of the code still relies on global state or direct resulting in a highly cyclical dependency which acts as the top level factory for services in MediaWiki which can be used to gain access to default instances of various services MediaWikiServices however also allows new services to be defined and default services to be redefined Services are defined or redefined by providing a callback the instantiator that will return a new instance of the service When it will create an instance of MediaWikiServices and populate it with the services defined in the files listed by thereby bootstrapping the DI framework Per $wgServiceWiringFiles lists includes ServiceWiring php
Definition injection.txt:37
This document describes the state of Postgres support in and is fairly well maintained The main code is very well while extensions are very hit and miss it is probably the most supported database after MySQL Much of the work in making MediaWiki database agnostic came about through the work of creating Postgres as and are nearing end of but without copying over all the usage comments General notes on the but these can almost always be programmed around *Although Postgres has a true BOOLEAN type
Definition postgres.txt:36
skin txt MediaWiki includes four core it has been set as the default in MediaWiki since the replacing Monobook it had been the default skin since then
Definition skin.txt:11