Re: [ZODB-Dev] ReadConflictErrors with ZODB3.10.1 and Relstorage 1.4.1

2011-01-26 Thread Jürgen Herrmann
On Wed, 26 Jan 2011 07:08:14 -0700, Shane Hathaway wrote: > On 01/26/2011 05:29 AM, Jürgen Herrmann wrote: >> _readCurrent >> is obviously reused and not cleared at transaction boundaries, is >> that >> expected?): > > No! Thanks for the great analysis. This insight is key. > > RelSto

Re: [ZODB-Dev] ReadConflictErrors with ZODB3.10.1 and Relstorage 1.4.1

2011-01-26 Thread Jürgen Herrmann
On Wed, 26 Jan 2011 07:08:14 -0700, Shane Hathaway wrote: > On 01/26/2011 05:29 AM, Jürgen Herrmann wrote: >> _readCurrent >> is obviously reused and not cleared at transaction boundaries, is >> that >> expected?): > > No! Thanks for the great analysis. This insight is key. > > RelSto

Re: [ZODB-Dev] ReadConflictErrors with ZODB3.10.1 and Relstorage 1.4.1

2011-01-26 Thread Shane Hathaway
On 01/26/2011 05:29 AM, Jürgen Herrmann wrote: > _readCurrent > is obviously reused and not cleared at transaction boundaries, is that > expected?): No! Thanks for the great analysis. This insight is key. RelStorage has a monkey patch of the Connection.sync() method, which has not change

[ZODB-Dev] ReadConflictErrors with ZODB3.10.1 and Relstorage 1.4.1

2011-01-26 Thread Jürgen Herrmann
i everybody! About a week ago i migrated our FileStorages to Relstorage instances. We have 5 databases, 4 of them mounted via ZodbMountPoints in a plain zope 2.13 installation. Since the migration i experience sporadic ReadConflictErrors (they occur about 1-4 hours after restarting the zop