Page MenuHomePhabricator

Database replication lag issues (tracking)
Closed, DeclinedPublic

Description

Author: zigger

Description:
This is a tracking bug for mediawiki issues caused by or made worse by database
replication lags between the master (used for updates) and the slaves (used for
reads).


Version: unspecified
Severity: normal

Details

Reference
bz1268
ReferenceSource BranchDest BranchAuthorTitle
repos/releng/scap!93review/dancy/check-for-mergeMessageFileList.php-warningsmasterdancyCheck for PHP notices during mwscript mergeMessageFileList.php
repos/releng/gitlab-cloud-runner!105upgrade-gitlab-runner-15-7-2mainjeltobump gitlab-runner image to 15.7.2
Customize query in GitLab

Event Timeline

bzimport raised the priority of this task from to Low.Nov 21 2014, 8:08 PM
bzimport set Reference to bz1268.
bzimport added a subscriber: Unknown Object (MLST).

arnomane wrote:

I personally think after I can easily reproduce Bug 1150 that this specific bug is no database lag issue. For details why I think so
see my last comments in that bugreport.

Is there any point on keeping this open? It says tracking but the task is totally empty and has not been used much.

Is there any point on keeping this open? It says tracking but the task is totally empty

"empty" where? It has three open sub tasks. But if it's not used, let's decline this ("tracking" tasks were a Bugzilla thing).

+1 for just archiving, we can use other tracking way instead of this task.

Declining as per the suggestion from Andre at T3268#3823818 as we don't use this ticket.