Kaushik Lingarkar fed1a54935 Refresh 'objects' dir and retry if a loose object is not found ... A new loose object may not be immediately visible on a NFS client if it was created on another client. Refreshing the 'objects' dir and trying again can help work around the NFS behavior. Here's an E2E problem that this change can help fix. Consider a Gerrit multi-primary setup with repositories based on NFS. Add a new patch-set to an existing change and then immediately fetch the new patch-set of that change. If the fetch is handled by a Gerrit primary different that the one which created the patch-set, then we sometimes run into a MissingObjectException that causes the fetch to fail. Bug: 581317 Change-Id: Iccc6676c68ef13a1e8b2ff52b3eeca790a89a13d Signed-off-by: Kaushik Lingarkar <quic_kaushikl@quicinc.com>		2023-01-13 18:44:35 +01:00
..
technical	Documentation/technical/reftable: improve repo layout	2020-02-11 11:52:35 +01:00
config-options.md	Refresh 'objects' dir and retry if a loose object is not found	2023-01-13 18:44:35 +01:00