Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multi-instance setups don't flush webhook events properly #13650

Closed
rijkvanzanten opened this issue May 31, 2022 · 0 comments · Fixed by #13651
Closed

Multi-instance setups don't flush webhook events properly #13650

rijkvanzanten opened this issue May 31, 2022 · 0 comments · Fixed by #13651
Assignees
Labels
Milestone

Comments

@rijkvanzanten
Copy link
Member

Describe the Bug

When you modify webhooks, the webhooks are re-registered. However, only the container that ran the original modification of webhooks is aware of this change. This causes the registered webhooks of the secondary instance to be out of sync, causing unexpected behavior when traffic is load balanced between the instances.

To Reproduce

Spin up two instances of Directus connected to the same DB & Redis server. Update webhooks on instance A, observer how the webhook doesn't fire when triggered from instance B.

Errors Shown

n/a

What version of Directus are you using?

49d8975

What version of Node.js are you using?

16.15.0

What database are you using?

Postgres 13.5 w/ Redis 6.2.6

What browser are you using?

n/a

How are you deploying Directus?

Locally

@rijkvanzanten rijkvanzanten self-assigned this May 31, 2022
@rijkvanzanten rijkvanzanten added this to the v9-next milestone May 31, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant