Hi,
I'm trying to make a replicated image repository. I want to have two
servers with big disks with the images stored on both of them (purely
for redundancy). When a new image is added to the repository it will
generally appear on one of the two servers before it appears on the
other (mostly by only a few seconds). Also, if one server crashes and
comes back, the new images that were stored in the mean time are not yet
available on both servers and will need to be rsynced. However, as soon
as the images are stored on 1 of the 2 servers, they must become available.
The only read access to the images from the outside world is via HTTP. I
was thinking of using pound to get the images from the backends,
however, there is only the small problem of (temporary) failure when an
image that is not yet on one of the two servers gets requested by pound
on the server where it's missing. In that case I would like pound to try
the other server (basically on a 404). Only if it gets a 404 from both
servers is it a REAL 404.
In the final solution I want to be able to send the requests to a
preferred server based on a header in the HTTP request, but from what I
saw, that should be doable with pound.
The question I have is, can I do the "404 failover" with pound, or do I
need to patch it? Is it easy to patch it for this use? Is this a good
way to go about it, or are there better solutions for the above
requirements?
Regards,
Sebastiaan
--
To unsubscribe send an email with subject unsubscribe to [email protected].
Please contact [email protected] for questions.
