On 06/18/2013 12:35 AM, Mahadevan, Venkat wrote:
I do not know why your environment is prone to trigger db_deadlock
(lot of replica agreements, VM, slow disks...).
I think the best way to progress is that you fill a ticket/bug so that
we may track the issue. Note this bug is possibly
On 06/18/2013 01:51 AM, thierry bordaz wrote:
On 06/18/2013 12:35 AM, Mahadevan, Venkat wrote:
I do not know why your environment is prone to trigger db_deadlock
(lot of replica agreements, VM, slow disks...).
I think the best way to progress is that you fill a ticket/bug so
that we may
Running in a VM should not be an issue if it follows the usual tuning
recommendation. But of course it adds a layer when investigating a RC.
What is weird is to hit so frequent (50) deadlock in a single DB call. In
addition it looks like it always happen when updating the CL so I can think to
