Re: High Availability Recommendation

> I'd love confirmation on that myself.
>
> If not, could you set it up so that both servers have READ access to
> the NFS FSFS repo but only one at a time has write access? I'd expect
> any load balancer could discriminate between GET and POST if you're
> using HTTP access. That way you wouldn't be wasting one of your CPUs
> most of the time.

CollabNet told me this would not work, because commits may have GET
requests in the midst of their transaction, and they must access the
same disk. With NFS if a GET that was part of a commit was redirected
to a second server whose NFS was cached and not seeing the latest
changes, it could cause problems.

I might be misunderstanding the details, but in any event they said
the idea above would work.

Justin

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 2 22:18:57 2007