to see the low quality of
the work that is done around SQL in OpenStack.
--
Julien Danjou
/* Free Software hacker
http://julien.danjou.info */
--
Peter Boros, Consultant, Percona
Telephone: +1 888 401 3401 ext 546
Emergency: +1 888 401 3401 ext 911
Skype: percona.pboros
-by InnoDB_rec_lock_wait:sum
digest-rec_lock_waits.txt
It will show what statements waited for locks most, these will most
likely be the ones causing the deadlock issues in case of multi-node
writing.
On Tue, May 20, 2014 at 2:27 PM, Peter Boros peter.bo...@percona.com wrote:
Hi,
I would like to shed some additional
for the additional details Peter. This confirms the parts I'd
deduced from the docs I could find, and is useful knowledge.
On Sat Feb 07 2015 at 2:24:23 AM Peter Boros peter.bo...@percona.com
wrote:
- Like many others said it before me, consistent reads can be achieved
with wsrep_causal_reads set
Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Peter Boros, Principal Architect, Percona
Telephone: +1 888 401 3401 ext 546
Emergency: +1 888 401 3401
