On Fri, Jul 1, 2022 at 12:07 PM ronnie sahlberg <ronniesahlberg@xxxxxxxxx> wrote: > > On Fri, 1 Jul 2022 at 16:03, Shyam Prasad N <nspmangalore@xxxxxxxxx> wrote: > > > > On Fri, Jul 1, 2022 at 3:23 AM Tom Talpey <tom@xxxxxxxxxx> wrote: > > > > > > Is there a justification for why this is necessary? > > > > > > When and how are admins expected to use it, and with what values? > > > > > > > Hi Tom, > > > > This came up specifically when a customer reported an issue with lease break. > > We wanted to rule out (or confirm) if deferred close is playing any > > part in this by disabling it. > > However, to disable it today, we will need to set acregmax to 0, which > > will also disable attribute caching. > > > > So Bharath now submitted a patch for this to be able to tune this > > parameter separately. > > Ok, will the option be removed later once the investigation is done? > We shouldn't add options that are difficult/impossible to use > correctly by normal users. We didn't intend to. We thought that this could be a useful tunable parameter that the basic users need not even worry about, but advanced users / developers could suggest changing it to tune / troubleshoot specific scenarios. > > > > > > > On 6/29/2022 4:26 AM, Bharath SM wrote: > > > > Adding a new mount parameter to specifically control timeout for deferred close. > > > > > > > > -- > > Regards, > > Shyam -- Regards, Shyam
