Mercury

If apache or mysql goes down, or you accidentally upload bad code to your drupal site, or you put your site into maintenance mode, apache gives varnish a 5xx. Varnish knows better than to cache this page, but it will serve it if the object grace has expired. Fortunately, varnish has the ability to reset the grace and serve the "good" page from cache until apache returns a non-5xx on that page.

Hello

Mercury 1.0 looking really good - nice work.

We have an anonymous website where we want everything to be cached by Varnish except

/somepage
/someotherpage

We set a couple of cookies (read by JS only, not Drupal) so I'd like to know whether we still need to strip these cookies via the.vcl file in order to force all pages to be cached?

Drupal users access the database via a different front end server that does not have Varnish running.

Thanks, James

I am planning on launching a multi-cty website that will cover 5 cities at first and then expand as time goes on.

Originally I had planned to run each city as a completely separate Drupal install, and possibly even on different servers completely. My thinking was splitting each city into a separate install might allow me to scale better since some cities may grow larger and more popular than others.

Now Im trying to think if that is the best route to take. After browsing around this group I am really interested to set my site up using Mercury on Amazon EC2 or Rackspace.

Hi

Have found Gear6 www.gear6.com.
They provide hosted memcache with automatic scaling. Sounds interesting.

Does anybody know, how to do it with memcache?

bennos

Anyone have a tip on making mercury's solr multi-core so it works with multi-sites?
There are some instructions over here though they use jetty method instead of tomcat
http://drupal.org/node/484800

Seems like the solr.xml included in mercury is ready for multiple cores and most of the instructions in the above post should do it?
Ive not tested with the existing mercury stuff but Ive failed at setting up a fresh multi-core solr, Im going to use the existing solr setup next test when I get some time.

Has anyone altered the mercury solr bit to account for multi-sites?

Sorry if this isn't the right place for this (point me to the right one and I'll go there), but I've encountered an issue with Varnish I can't seem to find help on the web for.

Starting today, at a random time (not sure what triggered it), every single page in the Drupal site started returning a 503 error, service unavailable (no additional information).

Over the past few days some of us have been discussing the aims and ambitions of this project:

http://drupal.org/project/esi

There are a lot of pieces to be developed to support this properly. My aim is to get something simple in place to allow blocks, regions and panels to be served out of an ESI cache. There are further ideas to build some sort of ESI-assembly into the Boost module, and to implement an intermediary cache layer between Drupal and an external ESI cache (e.g. Varnish) to prevent multiple bootstraps.

So, let's take this discussion out to the wider community!

I got a Mercury AMI instance up and running. This is my first time using AWS, so it's a bit of an exploration process for me.

After installing imagecache and image api, I see this warning in the Drupal status report.

<

blockquote>
GD Image Filtering Low Quality / Poor Performance