From: Terry Ewing (sun@deadtrout.com)
Date: Fri Aug 23 2002 - 11:51:01 EDT
All,
We've been looking into the idea of using cachefs in our data center. We
have a number of Netra T-1 edge server machines running Apache + mod_perl to
do some minor page assembly. They pull all the content out of static files
mounted from a backend NetApp F810 filer. We have been thinking that
cachefs may work well on each edge server box in order to ensure that at
least some of the content can still be delivered if we have a backend NFS
failure.
We've run into a number of problems. Running in connected mode cachefs
works fine. It checks for page changes on the NFS server and serves either
new content from the NFS server or the cached content from the local box.
In disconnected mode we run into a problem. Because of the nature of
connected/disconnected/demandconst modes we are not getting what we need.
The edge servers are mounting the partiton as read-only. A backend
server is creating static html pages at a frequent rate. We wanted
something on each edge server that would cache the most recent requests and
be able to continue serving in a backend failure. When there is no backend
failure we need the edge servers to always be checking to make sure they are
serving the most recent content.
This brings about 2 questions:
1) Of all I have read about CacheFS I'm not seeing people using it in data
centers. It seems that most uses are for workstations to store code
libraries and such. Am I going the wrong path by trying to use this
technology on servers that will be supporting moderate to high volume?
2) Is there a way to make it work in the way I want? I want it to
constantly check for new content, but if there is a network failure or a NFS
failure I want it to serve from local cache.
Thanks,
Terry Ewing
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:24:50 EDT