Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jürgen Kartnaller wrote:
We also run into this kind of problems.
The only save way to solve it was to serialize our index updates.
We do this by using one zope instance which runs only a
lovely.remotetask task service. This
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jürgen Kartnaller wrote:
> We also run into this kind of problems.
>
> The only save way to solve it was to serialize our index updates.
>
> We do this by using one zope instance which runs only a
> lovely.remotetask task service. This service cont
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joachim Schmitz wrote:
>>> Any suggestion for a temporary fix would be very welcome, since we get
>>> about 6000 conflict errors per day now about 15 % unresolved, and they
>>> are really killing our portal.
>> A workaround might be to replace the Da
Any suggestion for a temporary fix would be very welcome, since we get
about 6000 conflict errors per day now about 15 % unresolved, and they
are really killing our portal.
A workaround might be to replace the DateIndexes for 'created' and
'modified' with FieldIndexes: you will see a big j
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joachim Schmitz wrote:
> Tres Seaver schrieb:
>>>
>>>
>>>
>>>
>>>
>>>
>>> {'Application': , 'ZGlobals': >> object at 0xb2739224>}
>>>
>>> What does this tell us ?
>> That is a "real" conflict: both transactions have inserted values into
>> the '
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joachim Schmitz wrote:
> some more findings:
>
> 1. The conflict error really happens on the Portalcatalog
> 2. It is a BTreesConflictError: BTrees conflict error at -1/47/47:
> Conflicting inserts which disguised as ConflictError, through the
> var
Tres Seaver schrieb:
{'Application': , 'ZGlobals': object at 0xb2739224>}
What does this tell us ?
That is a "real" conflict: both transactions have inserted values into
the 'created' date index's '_index' under the same key, which can't be
resolved. Retrying the transaction is the
some more findings:
1. The conflict error really happens on the Portalcatalog
2. It is a BTreesConflictError: BTrees conflict error at -1/47/47:
Conflicting inserts which disguised as ConflictError, through the
various try: excepts:
3. It happens on DateIndexes like "created" and "modified".
Summary of messages to the zope-tests list.
Period Thu May 31 12:00:00 2007 UTC to Fri Jun 1 12:00:00 2007 UTC.
There were 5 messages: 5 from Zope Unit Tests.
Tests passed OK
---
Subject: OK : Zope-2.7 Python-2.3.6 : Linux
From: Zope Unit Tests
Date: Thu May 31 20:51:43 EDT 2007
URL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joachim Schmitz wrote:
> Tres Seaver schrieb:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Not if the sessions being used are from 'faster' -- it doesn't use
>> IOBTree. The major "application" use of that module is in the catalog.
>>
> y
one very important finding:
tryToResolveConflict fails in the resolve function
resolve object at 0xb1ab82b4>
by raising an exception, when I call it again from the debugger I get.
(Pdb) resolved = resolve(old, committed, newstate)
*** BTreesConflictError: BTrees conflict error at -1/47/47: Co
Tres Seaver schrieb:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Not if the sessions being used are from 'faster' -- it doesn't use
IOBTree. The major "application" use of that module is in the catalog.
you correct see below:
Try dumping out the contents of the bucket:
for k, v in buck
12 matches
Mail list logo
