NETOBSERV-447: Changed default FLP retry value to prevent FLP beeing oom-killed

[OlivierCazade]

No description provided.

[jpinsonneau]

Does this means we would have only 3 queries in total during a 10s frame before dropping flows ?

If loki is down, should we get the /ready enpoint result before retrying ?

[jotak]

I think that's a good change. If there's too many outstanding requests, it's FLP that is going to suffer.

Does this means we would have only 3 queries in total during a 10s frame before dropping flows ?

Not sure to get what you mean; to my understanding, the retry mechanism is most often used when rate limit is hit; but the problem is, rate limit is hit in general because FLP processes flows faster than what Loki can handle, so retrying is only post-poning the issue for later and even worsen it as it increases the number of queries to loki. So, in any case that's a "bad" situation, but failing fast prevents the situation to degrade even more.

[jotak]

lgtm

[OlivierCazade]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: OlivierCazade

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [OlivierCazade]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment