[development] drupal.org caching too aggressive?
nnewton at osuosl.org
Thu Dec 6 03:40:50 UTC 2007
I'll be looking at this, but I really doubt its replication delay at
this point...especially the stories about 6 minute delays, we only
fall even close to that far behind when someone is doing large db
imports and I usually yank the slave out of rotation when I get paged
However, it is possible so I'll take a look and see if I can setup
warnings on a finer grained basis.
On Dec 5, 2007 5:42 PM, Gerhard Killesreiter <gerhard at killesreiter.de> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Gerhard Killesreiter schrieb:
> > Derek Wright schrieb:
> >> On Dec 5, 2007, at 11:26 AM, Dave Cohen wrote:
> >>> I suspect that I'm seeing a cached page after posting the comment
> >>> (although I am logged in). Is this what's going on?
> >> No. You're probably seeing the page as one of the secondary database
> >> servers thinks it exists. There's replication delay, now that we have a
> >> cluster of DB servers, not just a single box. One of the costs of
> >> scalability...
> > I don't think this really applies. The only queries that get directed to
> > the slave are pager and search queries. The query that gets comments is
> > neither.
> That's actually wrong, it is a pager query. We probably shoudl discuss
> on how to pass a "this query is currently not pager safe"-parameter to
> the database layer.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> -----END PGP SIGNATURE-----
OSU Open Source Lab
More information about the development