-
-
Notifications
You must be signed in to change notification settings - Fork 387
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
Webhook loadbalancing does not work from VerneMQ #2072
Comments
@henningw thanks, yes, that's not implemented. Is the reason you tried to set this up actual performance issues with 1 endpoint? (it mostly matters for MQTT registers, not publish and subscribes where the authorization calls hit the WebHooks cache). 👉 Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq |
@henningw See your point. The thing is Verne needs to hit the authentication endpoint really for every single register, as it's the source of truth here. Caching seems problematic. 👉 Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq |
Environment
VerneMQ Version: 1.12.5
OS: CentOS (VerneMQ in docker debian 11)
Erlang/OTP version (if building from source): 24
VerneMQ configuration (vernemq.conf):
vmq_webhooks.mywebhook11.hook=auth_on_register
vmq_webhooks.mywebhook11.endpoint=http://10.128.0.1:8090/XXX/api/auth/v1/vernemq/register
vmq_webhooks.mywebhook12.hook=auth_on_subscribe
vmq_webhooks.mywebhook12.endpoint=http://10.128.0.1:8090/XXX/api/auth/v1/vernemq/subscribe
vmq_webhooks.mywebhook13.hook=auth_on_publish
vmq_webhooks.mywebhook13.endpoint=http://10.128.0.1:8090/XXX/api/auth/v1/vernemq/publish
vmq_webhooks.mywebhook13.no_payload=on
vmq_webhooks.mywebhook21.hook=auth_on_register
vmq_webhooks.mywebhook21.endpoint=http://10.128.0.2:8090/XXX/api/auth/v1/vernemq/register
vmq_webhooks.mywebhook22.hook=auth_on_subscribe
vmq_webhooks.mywebhook22.endpoint=http://10.128.0.2:8090/XXX/api/auth/v1/vernemq/subscribe
vmq_webhooks.mywebhook23.hook=auth_on_publish
vmq_webhooks.mywebhook23.endpoint=http://10.128.0.2:8090/XXX/api/auth/v1/vernemq/publish
vmq_webhooks.mywebhook23.no_payload=on
Cluster size/standalone:
standalone
Expected behaviour
VerneMQ should balance the webhook connections to two HTTP endpoints.
Actual behaviour
VerneMQ is only sending requests to the first configured webhook server
Output from vmq-admin
The text was updated successfully, but these errors were encountered: