On 01/02/2011 04:11, Shane Hathaway wrote:
My guess is that the zap_all took so long that the server had gone away
by the time the sql statement had be executed.
My guess is MySQL is configured to drop connections when they are idle.
Indeed, Rackspace had configured a wait-timeout of 60
Hi Shane,
I notice that one of my history-free storages only has 'new_oid' and
'object_state' tables while all the others have 'new_oid', 'object_ref',
'object_refs_added', 'object_state' and 'pack_object' tables.
What's special about this storage?
I also note that while the ones with lots of
Hi All,
I've had a couple of instances now where RelStorage-backed ZODB client
processes have crashed/segfaulted. As best I can tell, both times have
been the result of the MySQL server being restarted while the client is
connected.
However, other server restarts haven't caused this problem,
On 01/02/2011 04:03, Shane Hathaway wrote:
On 01/31/2011 06:30 PM, Chris Withers wrote:
Hi Shane,
I got the following error when trying to run zodbconvert against a
clustered MySQL environment running RHCS:
File
On 01/02/2011 14:42, Stephan Richter wrote:
On Tuesday, February 01, 2011, Chris Withers wrote:
I also note that while the ones with lots of tables have this schema for
object_state:
CREATE TABLE `object_state` (
`zoid` bigint(20) NOT NULL,
`tid` bigint(20) NOT NULL,
`state`
On 02/01/2011 10:16 AM, Chris Withers wrote:
I notice that one of my history-free storages only has 'new_oid' and
'object_state' tables while all the others have 'new_oid', 'object_ref',
'object_refs_added', 'object_state' and 'pack_object' tables.
What's special about this storage?
It
On 01/02/2011 17:33, Shane Hathaway wrote:
What's special about this storage?
It sounds like RelStorage didn't get a chance to finish creating the
schema. In MySQL, DDL statements are not transactional, so errors during
schema creation (such as a timeout) leave a partial schema.
Sounds like
On 02/01/2011 10:01 AM, Chris Withers wrote:
OperationalError: (2006, 'MySQL server has gone away')
...which feels a little on the serious side for (what is for MySQL)
quite a normal situation to be in.
Random disconnects are unacceptable for RelStorage. If MySQL goes away
outside
Hi Shane,
On 01/02/2011 17:45, Shane Hathaway wrote:
On 02/01/2011 10:01 AM, Chris Withers wrote:
OperationalError: (2006, 'MySQL server has gone away')
...which feels a little on the serious side for (what is for MySQL)
quite a normal situation to be in.
Random disconnects are
On 02/01/2011 07:35 PM, Chris Withers wrote:
On 01/02/2011 17:33, Shane Hathaway wrote:
What's special about this storage?
It sounds like RelStorage didn't get a chance to finish creating the
schema. In MySQL, DDL statements are not transactional, so errors during
schema creation (such as a
On 02/01/2011 07:51 PM, Chris Withers wrote:
I can understand the problem being fairly terminal if there was a
disconnect *during* a timeout, and I'd expect an exception, but not a
segfault ;-)
I haven't seen segfaults except when the dynamic linker used an
incorrect library. Use ldd to
Only to give some feedback:
I had similar issues on past and now I follow some rules:
- pack only with zodbpack
- pack-gc = false
- pack when the database is not been active update or not update at all.
But it does not imply RelStorage bug, since MySQL is know to not be so safe.
I'm happy
On Tue, Feb 1, 2011 at 3:52 PM, Shane Hathaway sh...@hathawaymix.org wrote:
On 02/01/2011 07:35 PM, Chris Withers wrote:
On 01/02/2011 17:33, Shane Hathaway wrote:
What's special about this storage?
It sounds like RelStorage didn't get a chance to finish creating the
schema. In MySQL, DDL
13 matches
Mail list logo
