Re: Using substanced with Zeo and keep getting database conflict errors

Jim Fulton <[email protected]>
Newsgroups gmane.comp.web.zope.zodb
Message-ID <CAPDm-Fj+uARW6WG_XvHFaJiTQzkVjAyhpB_9e_nmn+6XVmoTpA@mail.gmail.com>
On Tue, Sep 13, 2016 at 9:48 AM, Jo Gilder <[email protected]> wrote:
> Hi,
>
> I have setup an instance of substanced which is a pyramid based cms using
> zodb.

...

> I've set this up before and it worked fine but this application gives me
> conflict errors if I try and write to the database from two different
> locations.
>
> ConflictError: database conflict error (oid 0x30, class
> BTrees.IOBTree.IOBTree, serial this txn started with 0x03b9e3ac20faca33
> 2016-09-13 13:32:07.729605, serial currently committed 0x03b9e3acb62e9
>
> This is happening when I try and add data programatically from a bash file
> running a python script at the same time as I add data via a web interface.
> Any ideas?
>
> I have the following versions -

... This is almost certainly an application issue.

In addition to ideas Jens mentioned (long transactions, accidental
write on read):

- Does the application, substanced, or your script retry transactions
when there are conflict errors?  Retrying will often mitigate
conflicts.

- Are the conflict errors for the same or same kind of object? The
errors should include object ids. From a Python prompt, you can use a
connection get message to load an object given an id.  See if there
are any patterns with conflicting objects.

I'd try asking this questions on the substanced mailing list, although
a lot of the people who are likely to help are probably also on this
one.

Jim

-- 
Jim Fulton
http://jimfulton.info

-- 
You received this message because you are subscribed to the Google Groups "zodb" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.