Project

General

Profile

Bug #5750

Index queue and delete action can conflict with one another

Added by ben leinfelder about 8 years ago. Updated about 8 years ago.

Status:
Resolved
Priority:
Normal
Category:
metacat
Target version:
Start date:
11/26/2012
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5750

Description

During DataONE CN replication testing, Chris was seeing delete/archive actions fail due to dangling FKs in the xml_index table. I theory is that the asynchronous indexing queue is inserting this entry after the delete action has tried to remove FK references but before the actual xml_documents removal is performed.

I think the long-term solution should be to inspect the index queue during a delete() action and remove the docid from the queue if it is present.

History

#1 Updated by ben leinfelder about 8 years ago

There's now a call to remove the indexing queue task for a docid that is being deleted.

#2 Updated by Redmine Admin almost 8 years ago

Original Bugzilla ID was 5750

Also available in: Atom PDF