+1 On Fri, Feb 28, 2020 at 1:15 PM Ernest Burghardt <eburgha...@pivotal.io> wrote:
> yes, it was just a transposition/typo when the defaults were > refactored/moved > > On Fri, Feb 28, 2020 at 1:14 PM Owen Nichols <onich...@pivotal.io> wrote: > > > +1 for bringing this fix to 1.12 (assuming the change was unintentional?) > > > > Any ideas how much performance improvement this is anticipated to > restore? > > > > > On Feb 28, 2020, at 1:06 PM, Ernest Burghardt <echobr...@apache.org> > > wrote: > > > > > > bumping this out to DevList as something went wrong in the mail > system... > > > > > > On 2020/02/28 19:27:42, Bruce Schuchardt <bru...@vmware.com.INVALID> > > wrote: > > >> During a refactor the default ack-wait-threshold was changed from 15 > to > > 51. This will affect any deployment that doesn’t set its own threshold. > > >> > > >> The ack-wait-threshold determines how long we wait for a response to a > > message, such as replication of a put(), before taking some action. > > >> > > > > >
