[zanata-bugs] [Bug 986145] Erratic behaviour during concurrent or cancelled TMX exports

bugzilla at redhat.com bugzilla at redhat.com
Mon Jul 22 04:38:29 UTC 2013


https://bugzilla.redhat.com/show_bug.cgi?id=986145

--- Comment #5 from Sean Flanigan <sflaniga at redhat.com> ---
The reason that Zanata stopped responding is that the JDBC connection pool
(default size 10) was exhausted.  This happened because the cancelled TMX
downloads continued to use connections for quite a long time.

https://github.com/zanata/zanata-server/pull/61 should ensure that cancelled
downloads are detected promptly.  A cancelled download should now finish just
as quickly as if the download were not cancelled, hopefully a little faster.

However, due to http://bugs.mysql.com/bug.php?id=42929 the JDBC driver still
has to consume the entire result set.  Now we could split up the queries so
that the result set is smaller, but this would complicate the implementation
quite a bit, especially with regards to transactions, and I believe it would
really hurt the performance of TMX downloads.

The implemented speed improvement should be enough to reduce the likelihood of
say 10 concurrent cancelled TMX exports happening, which would cause Zanata to
become non-responsive.  A fix for bug 986741 should be able to prevent it
entirely.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=kPQJQSIlNE&a=cc_unsubscribe




More information about the zanata-bugs mailing list