On Tue, Sep 17, 2024 at 01:46:39PM -0400, karthik nayak wrote: > Patrick Steinhardt <ps@xxxxxx> writes: > > [snip] > > > +reftable.lockTimeout:: > > + Whenever the reftable backend appends a new table to the stack, it has > > + to lock the central "tables.list" file before updating it. This config > > + controls how long the process will wait to acquire the lock in case > > + another process has already acquired it. Default is 1000 (i.e., retry > > + for 1 second). > > Isn't the default 100ms? As that was what was mentioned in the commit > message Oh, yeah. I ended up changing it. 1 second is the default timeout used by packed-refs, 100ms is the default timeout used by loose refs. The reason why I ultimately picked 100ms over 1s is that our usecase is closer to loose refs, because it is our "normal" code path that we hit whenever we write reftables. Will fix. Patrick
