[5.8.4] spam of emqx_session_mem_unknown_message EXIT message #14526
Unanswered
simon-jouet
asked this question in
Q&A
Replies: 1 comment 1 reply
-
Hi @simon-jouet, thanks for bringing this up. I wasn't able to quickly reproduce it but I'm pretty confident that it's a bug: these stray warnings should not be here, regardless of the configuration. We'll try to dig it more thoroughly, I'd appreciate if you file a bug report in the meantime. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
Thanks for EMQx, I'm currently migrating a system to use it and so far it's been working really well in a 3 node cluster on kubernetes.
I have an issue that looks similar to #14198 and #14197 but I'm running 5.8.4 and not 5.8.1.
It might me a configuration issue but I can't really find any details unfortunately on what might be wrong.
In my logs I have a lot of errors bulked by clientId (snippet from the last few lines of the logs)
The clients are connected over websocket. ingress-nginx is acting as the termination for TLS. The cluster is made of 3 servers with plenty of resources available, and each node is handling at the moment ~60 connections and ~160 subscriptions.
An overview of the cluster from the UI, if that's of any help (I was originally trying to figure out the dropped messages...)
Beta Was this translation helpful? Give feedback.
All reactions