Datadeploy Deadlock on Batch Metadata Update

nickcolorado

Hi,

When performing a batch update on a metadata field in TeamSite, after performing the update datadeploy tries to update the workarea metadata tables with the new metadata values. During this update it trips over itself and creates a deadlock situation in the database. Here's a more detailed description of how to recreate the problem:

We have a metadata field 'expiration_date'. We update all 2000 files in a workarea with a new expiration date. This 'batch update' to a new expiration date causes thousands of messages to be written to the event subsystem. These messages are seen by Datadeploy workarea synchronization (also known as DAS) and are processed to update the workarea metadata tables. During the processing of these messages, DAS trips over itself and causes a deadlock situation in the database.

Has anyone else seen this behavior? Does anyone know how to prevent the deadlock from occuring?

Thanks,
Nick

Trey

I've seen this too. Sorry, I don't know of a fix but would be inerested in hearing one.