Hi we started receiving the errors below after we used the zope 2 undo tab
to undo an accidental delete of an item in Plone. We have 2 Zope instances
and the error only occurred in one (many times until I restarted the
server). I'm wondering if this is a known relstorage bug?
yours
Anthony
201
Some results I thought some people might be interested following our
upgrade from Relstorage 1.4.1 to 1.5. I've only upgraded our test
system but that is a clone of live with a db size of 6631MB running
Plone 3.3.
Before the upgrade the pack was taking 2 hours 15 minutes. After the
pack 8 minute
this hit manageable?
* Can we put anything in place to mitigate this?
* Would you simply recommend having the existing mysql + zope on one server and
the new mysql + zope on the other?
Thanks in advance
Anthony
___
Anthony Gerrard
Email: a
Hi,
The Relstorage pypi site recommends against using version 5.1.23 of MySQL
because of "major bugs". As it doesn't state explicitly what these bugs are I
can't tell whether they're fixed in the latest version (5.1.32). Does anyone
know whether it's safe to use this latest version of MySQL 5
OK thanks. To confirm you can have a cluster of Zope instances all using
relstorage to connect to the same database. This negates the need for ZEO as
the database handles the multi-threaded data access.
+-+ +-+
|Zope Server 1| |Zope Server 2|
+-+ +
Hi,
I'm working on a project to migrate a number of sites to a content management
system. We finished our evaluation period and chosen Zope / Plone. I'm new to
both products and would like some advice about our initial deployment. The
impression I get is that using both ZEO and Relstorage ar
