Re: ZEO caching,was Re: [Zope-dev] more Zope2.6 fun: ZEO client death.
OK... more info... here's my setup. 1 ZEO server, 3 clients (client 1, client 2, client 3). client 1 is on the same physical machine as the server. client 2 is on a different machine, but close by on a high-bandwidth network. client 3 is on a third machine on the same network. If I make changes on client 1: they are not seen on client 2 OR client 3 until I flush the database cache on that client. If I make changes on client 2: they are immediately seen on client 1. client 3 does not see them until i flush its database cache. If I make changes on client 3: they are immediately seen on client 1. client 2 does not see them until i flush its database cache. I noticed that the system time on each machine was a bit off, but that doesn't seem to be the culprit; they're very close now, and it makes no difference which one is ahead of the other: I get the same behavior described above regardless of whether clients 2 and 3 are slightly ahead or slightly behind client 1. Next, will investigate ZEO logs as Shane suggested... -- Paul Winkler http://www.slinkp.com Look! Up in the sky! It's NEGA SOCK IN PARIS! (random hero from isometric.spaceninja.com) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
ZEO caching, was Re: [Zope-dev] more Zope2.6 fun: ZEO client death.
On Thu, Jul 31, 2003 at 10:06:08AM -0400, Shane Hathaway wrote: Jim and PythonLabs put a bunch of work into optimizing ZEO cache validation earlier this year, and now it's quite speedy. Which reminds me... Is it expected that ZEO can take quite a while to show a new object on all clients? With zope 2.6.2b3, ZEO 2.0.2, I can reliably get this behavior: 1) browser 1 looking at foofolder on client 1 adds a new object /foofolder/bar. 2) browser 2 on client 2 visits /foofolder/bar. Not found. 3) browser 2 on client 2 flushes the browser cache, quits / restarts the browser, etc. /foofolder/bar again. Still not found. 3.5) Repeat step 3 intermittently for an hour (!). Not found. 4) client 2 is restarted. Browser 2 refreshes and immediately gets the expected object bar. This is clearly problematic. At what point is client 2 supposed to see the new object?? -- Paul Winkler http://www.slinkp.com Look! Up in the sky! It's SADIST ITE! (random hero from isometric.spaceninja.com) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: ZEO caching, was Re: [Zope-dev] more Zope2.6 fun: ZEO client death.
On Thu, Jul 31, 2003 at 12:13:40PM -0400, Shane Hathaway wrote: This is clearly problematic. At what point is client 2 supposed to see the new object?? Immediately. You are experiencing a bug. ;-) OK... is this a known bug? Is it a bug in ZEO or Zope or what? -- Paul Winkler http://www.slinkp.com Look! Up in the sky! It's MAFIOSO LETTUCE-WAVER ! (random hero from isometric.spaceninja.com) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
