Skip to content

Disable primary stickiness for WebHookService

Matthias Käppler requested to merge 324376-disable-primary-stickiness into master

What does this MR do?

This change disables primary stickiness in load balanced environments for the WebHookService response handler.

We hope that this will make it more likely for this worker to go to replicas for reads. Full context in this issue: #324376 (closed)

In short, we think that because these writes are merely logging and updating hook statistics, we won't be reading stale data even when going to replicas.

Note that I decided to put this behind the same FF as the load-balancing feature for the worker calling into this service (#331365 (closed)) since this is logically part of the same rollout. We disabled the feature for now because the results were not adequate, and are hoping that this additional change might make it more impactful. I will either roll back all changes or none.

Does this MR meet the acceptance criteria?

Conformity

Availability and Testing

Related to #324376 (closed)

Edited by Matthias Käppler

Merge request reports

Loading