From: Alex <ajb44.geo@yahoo.com>
To: git@vger.kernel.org
Subject: Re: Multiple clients accessing git over NFS
Date: Tue, 16 Nov 2010 13:47:02 +0000 (UTC) [thread overview]
Message-ID: <loom.20101116T144422-559@post.gmane.org> (raw)
In-Reply-To: AANLkTimyFkVFAw4s2fiWKZFPvnx15K6U6GbxmRgznx7Z@mail.gmail.com
Khawaja Shams <kshams <at> usc.edu> writes:
>
> Is it a recommended practice to share a repository over NFS, where
> multiple clients can be pushing changes simultaneously? In our
> production environment, we have a Git repository setup behind
> git-http-backend. We would like to place multiple Apache servers
> behind a load balancer to maximize availability and performance.
> Before we proceed, we wanted to check to see if this practice has a
> potential to cause repository corruption. If there are other ways
> others have solved this problem, we would be very interested in
> learning about those as well. Thank you.
>
Others have commented on the git aspects of this, but FYI there is a handy
program here: http://www.unixcoding.org/NFSCoding#NFS_Cache_Tester
that tests aspects of your NFS implementation. (Sadly the one we have
at work is crap, or at least it was last time I ran the program).
Alex
prev parent reply other threads:[~2010-11-16 13:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-14 21:24 Multiple clients accessing git over NFS Khawaja Shams
2010-11-14 23:11 ` Greg Troxel
2010-11-14 23:42 ` Khawaja Shams
2010-11-15 0:32 ` Jonathan Nieder
2010-11-15 19:56 ` Jan Hudec
2010-11-15 20:44 ` Drew Northup
[not found] ` <AANLkTinX-XR2TaZPGPeWyekMq3e8wEDkfcmi_o6pTvMK@mail.gmail.com>
2010-11-14 23:46 ` Greg Troxel
2010-11-15 16:24 ` J. Bruce Fields
2010-11-15 1:26 ` Sitaram Chamarty
2010-11-16 13:47 ` Alex [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20101116T144422-559@post.gmane.org \
--to=ajb44.geo@yahoo.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.