[Erp5-dev] Delayed reindex, workflow script and acquisition

Boris Kocherov bk at raskon.org
Tue Nov 16 15:36:32 CET 2010


Hello,
 Sincere respect for GREAT work to everybody who is solving the issue.

On 16/11/10 14:57, Leonardo Rochael Almeida wrote:
> Em Ter, 2010-11-16 às 11:34 +0100, Julien Muchembled escreveu:
> > The bug you experienced is a combination of 3 known bugs, 2 of them being already fixed in trunk:
> > 
> > 1. The first bug only exists with Zope 2.8 and a backport from Zope 2.12 was committed to ERP5/r35627
> >     This bug is specific to ZEO environments.
> > 
> > 2. The second bug is also in Zope/ZODB code and is specific to ZEO environments.
> >     It is tested by TestInvalidationBug.testLateInvalidationFromZEO
> >      and a fix was committed to r39710
> >     We still need to discuss with Zope developers to fix ZODB.
> > 
> > 3. The third bug affects all kinds of multi-node zopes: ZEO clusters but also single-process with several threads.
> >     It is tested by TestInvalidationBug.testCommitOrder
> >     Although this bug is specific to ERP5, a proper fix would require
> > some changes in Zope code and we are still discussing with them. I've
> > attached a temporary patch.
> 
> A small correction. The changes that would be necessary in Zope code
> have already landed[1] (and subsequently that part of code was removed
> from Zope2 core into an external package (Products.ZSQLMethods) by Zope
> the developers).
> 
> [1] http://svn.zope.org/Zope/branches/2.12/src/Shared/DC/ZRDB/TM.py?rev=113622&r1=110405&r2=113622
> 
> The only thing pending before merging to trunk the fix attached by
> Julien is a resolution to an internal discussion on whether it's better
> to protect against data migration by having a specific ZMySQL adapter
> subclass with the right .sortKey() method (which would need a code
> update and restart if the sortKey() method of ZEO and FileStorage
> changed), or if we're going to protect against Zope restarts by
> continuing to use a generic ZMySQL adapter for CMFActivity, and
> requiring a data migration to change the .sortKey() value in case of
> changes in the sort order of ZEO/FileStorage (which would only happen in
> case of a code migration to a different version of ZEO/FileStorage that
> would have required a restart anyway).

Best regards,
    Boris Kocherov



More information about the Erp5-dev mailing list