Mounted Storage / ZEO startup delay (30 seconds)
I'm using MountedStorage to share a common ZODB between multiple Zope instances. I'm using persistant client cache. yet every time I restart/startup my server, there's a 30 second delay incurred when accessing the storage. I'm wondering where this delay is coming from? Perhaps a reverse DNS timeout? I'm connecting on localhost, which is in /etc/hosts, so I don't think that's it. Ideas? 2002-10-08T15:23:50 INFO(0) ZEC cache opened. current = 0 ------ 2002-10-08T15:23:50 INFO(0) ClientStorage 8874 Connected to storage via <ManagedConnection ('127.0.0.1', 4400)> ------ 2002-10-08T15:24:20 INFO(0) ClientStorage 8874 registerDB(<ZODB.DB.DB instance at 0x832fc6c>, None) Brad Clements, bkc@murkworks.com (315)268-1000 http://www.murkworks.com (315)268-9812 Fax AOL-IM: BKClements
On 8 Oct 2002 at 16:51, Toby Dickenson wrote:
On Tuesday 08 Oct 2002 4:28 pm, Brad Clements wrote:
I'm using persistant client cache.
It could be validating the client cache. try deleting those files, and restart.
No effect. It is EXACTLY 30 seconds delay. there must be a timeout somewhere, but I can't find it in the ZEO server or client code. any suggestions on what happens between the last two statements? 2002-10-08T18:26:39 INFO(0) ZEC cache opened. current = 0 ------ 2002-10-08T18:26:39 INFO(0) ClientStorage 1822 Connected to storage via <ManagedConnection ('127.0.0.1', 4400)> ------ 2002-10-08T18:27:09 INFO(0) ClientStorage 1822 registerDB(<ZODB.DB.DB instance at 0x8ec5744>, None) Brad Clements, bkc@murkworks.com (315)268-1000 http://www.murkworks.com (315)268-9812 Fax AOL-IM: BKClements
participants (2)
-
Brad Clements -
Toby Dickenson