If I have zimbraHttpDosFilterMaxRequestsPerSec set to something too low like 10 and I perform an import with concurrency set to something bigger like 50, then items could fail to be imported given the likelihood of zimbraHttpDosFilterMaxRequestsPerSec blocking the incoming connection? If it fails, does the import stop completely or does it keep going and moves on to the next item?

I wonder if setting zimbraHttpDosFilterDelayMillis to 0 before the import vs the default -1 would allow the import to complete vs guessing at the proper value and trying to maximize the zimbraHttpDosFilterMaxRequestsPerSec so that the import could complete the fastest.

% zmprov desc -a zimbraHttpDosFilterDelayMillis
zimbraHttpDosFilterDelayMillis
Delay imposed on all requests over the rate limit, before they are
considered at all. -1 = Reject request, 0 = No delay, any other value
= Delay in ms

type : integer
value :
callback :
immutable : false
cardinality : single
requiredIn :
optionalIn : server,globalConfig
flags : serverInherited
defaults : -1
min :
max :
id : 1430
requiresRestart : mailbox
since : 8.0.3
deprecatedSince :

Jim

Resultados de traducción

Hi @rasputia,

Probably this is caused by the DOS filter: please, check its value with

zmprov gcf zimbraHttpDosFilterMaxRequestsPerSec

and, if it is less than 100, set it at least to 100 with

zmprov mcf zimbraHttpDosFilterMaxRequestsPerSec 100

Resultados de traducción