diff options
author | Christian Halstrick <christian.halstrick@sap.com> | 2014-11-06 17:58:01 +0100 |
---|---|---|
committer | Matthias Sohn <matthias.sohn@sap.com> | 2014-11-12 00:41:35 +0100 |
commit | 0fc8b05a71054311c6290f6408386f7c48409724 (patch) | |
tree | 7baa01c22198365a299752f886cad0793f2f45fc /org.eclipse.jgit.junit.http | |
parent | da178eedd284c1e9ad87191d287939329ea8d0a5 (diff) | |
download | jgit-0fc8b05a71054311c6290f6408386f7c48409724.tar.gz jgit-0fc8b05a71054311c6290f6408386f7c48409724.zip |
Introduce config parameter core.trustfolderstat
JGit's ObjectDirectory implements the optimization that it remembers the
pack folders (.git/objects/pack) lastModified timestamp and doesn't
check for new packfiles in this folder if the lastModified attribute has
not changed.
In environments using NFS this can cause trouble. If multiple JGit
instances from multiple machines work on the same repository and one
instance creates a new ref and a new packfile (e.g. by doing a fetch)
then the other machines may detect the new ref but can't resolve the
referenced object because it doesn't detect that pack folder has a new
packfile. That's because NFS may cache file/folder metadata for quite a
long time and the pack folders modification time is not updated although
a new packfile is there and could be read.
The new config parameter core.trustfolderstat controls this behaviour.
The default is true and jgits behaviours is unchanged. But if this
parameter is set to false then jgit doesn't trust the pack directories
lastmodified anymore. Instead it will always iterate through the content
of that folder to detect new packfiles.
Change-Id: Ie3b4e92933286aa9916070a22422e629b3147f54
Signed-off-by: Matthias Sohn <matthias.sohn@sap.com>
Diffstat (limited to 'org.eclipse.jgit.junit.http')
0 files changed, 0 insertions, 0 deletions