actually it is possible to disable transaction? i believe the cluster will
handle auto-recommit except for transactional commit.
On Saturday, July 20, 2013 4:39:01 PM UTC+7, vince wrote:
>
> i think the framework errors are from web2py session update into mysql,
> we've already use session.fo
i think the framework errors are from web2py session update into mysql,
we've already use session.forget to minimize the problem but still we need
to update session sometimes.
we have already catching all update request and do retry ourself. since
mariadb galera cluster is synchronous replicati
>
> i do not know which function actually causing this problem. the
> application we testing are mostly select query so most likely it's from the
> web2py session update query.
I think this is a workflow issue. Perhaps your db error occurs after
executing the action logic. In that case, this
i do not know which function actually causing this problem. the application
we testing are mostly select query so most likely it's from the web2py
session update query.
in pymysql/connection.py
def commit(self):
''' Commit changes to stable storage '''
try:
self
> the sample from you didn't work.
Can you post the new error output?
--
---
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 web2py+unsubscr...@googlegroups.c
actually yes i just need a way to handle this error myself. see the above
for the error message i attached, the sample from you didn't work.
On Thursday, July 18, 2013 6:56:27 AM UTC+8, Alan Etkin wrote:
>
> those ticket don't come with request/session info, we have no idea where
>> and when di
>
> 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?
>
AFAIK, web2py does not retry db I/O commands. The tickets are created when
the request generates an uncaught exception (in y
ehm, sorry. are you blaming web2py or the galera cluster ? web2py doesn't
do anything special unless sending SQL queries down the pipe. If your
galera cluster goes into deadlocks executing queries, fix the cluster ^_^
--
---
You received this message because you are subscribed to the Google G
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/web2
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 com
10 matches
Mail list logo
