Just to close my question: I tweaked few settings for innodb and seems pretty good already.
The biggest is being: transaction_isolation = READ-COMMITTED Of course not for everyone but for my needs, this works perfectly. thanks On Thursday, June 27, 2013 8:36:51 PM UTC-7, Srini wrote: > > I guess my question should have been how do I handle consistent non > locking reads as app server is reverse proxied and each request goes to > different session. > > thanks > > On Thursday, June 27, 2013 8:11:38 PM UTC-7, Srini wrote: >> >> Hi, >> >> I am using tornado, sqlalchemy behind ngnix in reverse proxy mode. I run >> 4+ app servers and each maintaining it's own db session and connection. >> >> I am seeing the same problem as mentioned in the forum. One session >> creates new data and other session doesn't get updated information. As I am >> behind reverse proxy, each user request could go to different session all >> together. >> >> >> https://groups.google.com/forum/#!searchin/sqlalchemy/multiple$20sessions/sqlalchemy/MqeoIcRAdwM/egleUsQ6z-8J >> >> How can I avoid this? I am using InnoDB. >> >> thanks >> >> -- 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 sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/groups/opt_out.
