i am using mariadb galera cluster and we did not implement any locking.
been testing this cluster for long and it will return locking error during
node lag.
heres the error i got.
Traceback
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
Traceback (most recent call last):
File "/home/web2py/gluon/main.py", line 599, in wsgibase
BaseAdapter.close_all_instances('commit')
File "/home/web2py/gluon/dal.py", line 560, in close_all_instances
db._adapter.close(action)
File "/home/web2py/gluon/dal.py", line 540, in close
getattr(self, action)()
File "/home/web2py/gluon/dal.py", line 1740, in commit
if self.connection: return self.connection.commit()
File "/home/web2py/gluon/contrib/pymysql/connections.py", line 631, in commit
self.errorhandler(None, exc, value)
File "/home/web2py/gluon/contrib/pymysql/connections.py", line 202, in
defaulterrorhandler
raise errorclass, errorvalue
InternalError: (1213, u'Deadlock found when trying to get lock; try restarting
transaction')
In file: Framework
On Wednesday, July 17, 2013 5:27:30 PM UTC+8, Massimo Di Pierro wrote:
>
> We need more information. What is galera cluster? What you trying to lock?
>
> On Tuesday, 16 July 2013 22:29:09 UTC-5, vince wrote:
>>
>> we are testing web2py with galera cluster and notice lots of Deadlock
>> found when trying to get lock; try restarting transaction ticket.
>>
>> those ticket don't come with request/session info, we have no idea where
>> and when did this problem occur. does that mean that web2py already handle
>> the retry?
>>
>
--
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
