Manual:$wgJobSerialCommitThreshold
From Linux Web Expert
| File:OOjs UI icon alert-destructive.svg | <translate> This feature was removed completely in version <tvar name=ver>1.42.0</tvar>.</translate> |
| <translate> Extensions</translate>: $wgJobSerialCommitThreshold | |
|---|---|
| Make job runners commit changes for replica DB-lag prone jobs one job at a time. |
|
| <translate> Introduced in version:</translate> | 1.26.0 (Gerrit change 205825; git #7c821cae) |
| <translate> Removed in version:</translate> | 1.42.0 (Gerrit change 974677; git #I19043e7) |
| <translate> Allowed values:</translate> | (float or boolean) |
| <translate> Default value:</translate> | false |
| <translate> Other settings:</translate> <translate> Alphabetical</translate> | <translate> By function</translate> | |
Details
Make job runners commit changes for replica DB-lag prone jobs one job at a time. This is useful if there are many job workers that race on replica DB lag checks. If set, jobs taking this many seconds of DB write time have serialized commits.
Note that affected jobs may have worse lock contention. Also, if they affect several DBs at once they may have a smaller chance of being atomic due to the possibility of connection loss while queueing up to commit. Affected jobs may also fail due to the commit lock acquisition timeout.
