On 8/22/15 12:15 PM, dewey wrote:
I'm creating my session like this:
engine = create_engine(_db_con_str, echo=DB_ECHO, pool_recycle=3600,
isolation_level="READ UNCOMMITTED")
Session = sessionmaker(bind=engine)
Session(expire_on_commit=False)
Is any of that the likely culprit??
not at all. your code has a deadlock, so this has to do with what
tables are being accessed, and how, and when. You need to isolate where
your application attempts to run two activities, likely on two separate
connections, concurrently. Looking at things like the processlist
view (https://dev.mysql.com/doc/refman/5.1/en/processlist-table.html) as
well as SHOW INNODB STATUS can be helpful here.
A google immediately turns up three decent stackoverflow threads, the
second one has some good details about inspecting transaction status:
http://stackoverflow.com/questions/19458960/mysql-error-code-1205-lock-wait-timeout-during-update-with-inner-join
# good answer about SHOW INNODB STATUS
http://stackoverflow.com/a/6005564/34549
http://dba.stackexchange.com/questions/21464/error-code-1205-lock-wait-timeout-exceeded-in-mysql
--
You received this message because you are subscribed to the Google
Groups "sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
To post to this group, send email to [email protected]
<mailto:[email protected]>.
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.
