P4DTI issue job000701

TitleA hanging query can lock up the defect tracker
Assigned userNick Barnes
DescriptionThe replicator may take some locks in the defect tracker during a replication poll. If the replicator hangs during the poll (for instance because a query made to Perforce or to the defect tracker hangs), these locks may interfere with normal operation of the defect tracker. This applies in particular to Bugzilla, where the replicator locks most of the Bugzilla tables in order to ensure it gets an atomic view of the Bugzilla state. A customer having problems with Perforce (caused by a Linux kernel bug) found that a Perforce query made by the replicator was hanging and that this prevented normal operation of Bugzilla [1].
AnalysisAll queries made by the replicator should have some sort of time out. Hitting the time out should cause a poll failure.
How foundcustomer
Evidence[1] <http://info.ravenbrook.com/mail/2003/05/19/20-59-59/0.txt>
Observed in1.5.3
Created byNick Barnes
Created on2003-05-20 17:14:00
Last modified byNick Barnes
Last modified on2018-07-05 17:28:07
History2003-05-20 NB Created.
       2018-07-05 NB Suspended because the P4DTI is obsolete.