git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Multiple clients accessing git over NFS

From
KSKhawaja Shams <kshams@usc.edu>
Date
Nov 14, 2010, 23:42 UTC
Message-ID
<AANLkTim1bUbofDzC5HJnB--0WkT45ewbWCa25RebEgae@mail.gmail.com>
In-Reply-To
<rmi39r3mrf6.fsf@fnord.ir.bbn.com>
Hi Greg,
   Thank you for the insightful response. We have multiple automated
clients pushing and pulling changes from git as events occur. We have
not hit any real performance issues just yet. Our main goal is to
improve the availability of the repository in case the box running the
apache server has an outage during a mission critical period. Any
other ideas on how to accomplish this? From your remarks, it sounds
like putting the git repository on NFS, even with a single client, can
be problematic due to the locking issues. Is that what you meant?
   I am still interested in knowing if git can handle multiple
simultaneous pushes on the same repository without encountering
corruption issues. Thank you.
Previous: Greg TroxelNext: Jonathan Nieder
Message 3 of 10 in “Multiple clients accessing git over NFS”
  1. Khawaja ShamsNov 14, 2010
  2. Greg TroxelNov 14, 2010
  3. Khawaja ShamsNov 14, 2010
  4. Jonathan NiederNov 15, 2010
  5. Jan HudecNov 15, 2010
  6. Drew NorthupNov 15, 2010
  7. J. Bruce FieldsNov 15, 2010
  8. Sitaram ChamartyNov 15, 2010
  9. AlexNov 16, 2010
  10. Greg TroxelNov 14, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.