Right…. Ok, that explains some of the issues.
From a design perspective… it would make sense if the RO updated the same row, or a row in a separate table. But not a different row in the same table. Outside of the additional RPC overhead, has anyone had a problem updating a row in a different table? If I understand correctly, there wouldn't be a chance of any 'deadlocks', just a bit of latency or the potential for an RPC error if you have a flakey network / nodes… On Oct 11, 2013, at 12:26 PM, Vladimir Rodionov <[email protected]> wrote: >>> With respect to the OP's design… does the deadlock occur because he's >>> trying to update a column in a different row within the same table? > > Because he is trying to update *row* in a different Region (and potentially > in different RS). > > Best regards, > Vladimir Rodionov > Principal Platform Engineer > Carrier IQ, www.carrieriq.com > e-mail: [email protected] > > ________________________________________ > From: Michael Segel [[email protected]] > Sent: Friday, October 11, 2013 9:10 AM > To: [email protected] > Cc: Vladimir Rodionov > Subject: Re: Coprocessor Increments > > > Confidentiality Notice: The information contained in this message, including > any attachments hereto, may be confidential and is intended to be read only > by the individual or entity to whom this message is addressed. If the reader > of this message is not the intended recipient or an agent or designee of the > intended recipient, please note that any review, use, disclosure or > distribution of this message or its attachments, in any form, is strictly > prohibited. If you have received this message in error, please immediately > notify the sender and/or [email protected] and delete or destroy > any copy of this message and its attachments. >
