Hi Syd,
> I'm guessing an an NFS share from the 2 webservers to the 1 fileserver. 
> However, from a bit of research with load balanced magento setups there seems 
> to be a lot of negative comments about using NFS in this way.

It's always better to avoid NFS as it introduce a point of failure.
Sometimes just syncing the files on both servers with rsync / unison /
snapshots /  whatever is preferable (it strongly depends on the number
of files and the number of file changes). A crashy NFS server can
leave inconsistent mount points on the webservers .

Anyway it works but you must qualify your server and client version
and setups before turning it in production. Avoid lockd unless it's
absolutely necessary, enable jumbo frames, find the good rsize, wsize,
check and recheck your disks health, your raids settings, your IO
performances. If possible, use varnish on the web servers for caching
static content or  serve the static files directly from the file
server using nginx.  Never forget that NFS is slow.

Joris


2013/5/29 Syd <[email protected]>:
> Hi There,
>
> I've setup a few small load balanced environments with haproxy usually 2
> LB's, 2+ webservers, 1 db server.
>
> However, I now have a client who needs the above but with an aditional file
> storage server for user uploads. So I'm arranging for an extra dedicated
> server with several TB that will be on private network with the 2
> webservers.
>
> The client uses a custom coded CMS which allows for a path to be specified
> for an "upload" folder for user file storage.
>
> Any simple advice for the best method to connect a file server to the web
> servers?
>
> I'm guessing an an NFS share from the 2 webservers to the 1 fileserver.
> However, from a bit of research with load balanced magento setups there
> seems to be a lot of negative comments about using NFS in this way.
>
>
>

Reply via email to