On 09/02/15 18:15, Jay Pipes wrote:
> On 02/09/2015 01:02 PM, Attila Fazekas wrote:
>> I do not see why not to use `FOR UPDATE` even with multi-writer or
>> Is the retry/swap way really solves anything here.
> <snip>
>> Am I missed something ?
> Yes. Galera does not replicate the (internal to InnnoDB) row-level locks
> that are needed to support SELECT FOR UPDATE statements across multiple
> cluster nodes.
> https://groups.google.com/forum/#!msg/codership-team/Au1jVFKQv8o/QYV_Z_t5YAEJ

Is that the right link, Jay? I'm taking your word on the write-intent
locks not being replicated, but that link seems to say the opposite.

Matthew Booth
Red Hat Engineering, Virtualisation Team

Phone: +442070094448 (UK)
GPG ID:  D33C3490
GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490

OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Reply via email to