On Sun, Feb 21, 2010 at 8:54 AM, André Warnier <a...@ice-sa.com> wrote:
>> it's uploads that >> add a file to the file system on the Tomcat that processed the request. >> And that would be the source filesystem to rsync from. > > Yes, but how often ? In the simplest case, once each time a file is uploaded :-) How frequent are the uploads? If it's one every few minutes, the above simplest case applies; if it's hundreds per second, different situation, tune to suit. > Each Tomcat would need to rsync is repository with each of > the others, constantly, not so ? Isn't that in itself going to generate a > lot of traffic ? And if each Tomcat "pulls" the files of the others via > rsync, how does one rsync know that the new file he is seeing on this other > Tomcat has finished uploading ? Again, the file system *with a new file* is the source for an rsync push. The application itself knows when an upload is complete, so there won't be incomplete files copied. > In my opinion, the simplest and most reliable scheme is to have one single > repository, which could itself be made as reliable as possible via a number > of methods (hardware duplication, replication, snapshots,..). Which certainly starts moving away from "simplest" :-) > If there are > locking issues, the single repository makes them easier to solve. If there > is only one "uploading host", that again makes it easier. I definitely agree with the second statement. -- Hassan Schroeder ------------------------ hassan.schroe...@gmail.com twitter: @hassan --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
