You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
same issure as #12177
but my clients are already set clean_start = true and Session-Expiry-Interval to 0,
but connections still can not remove by it self
What did you expect to happen?
After all connections are disconnected, the dashboard displays 0 connections
How can we reproduce it (as minimally and precisely as possible)?
The error appeared by letting the cluster run for more than one day and connecting / disconnecting a large amount of client, during this period, one core node was restarted once
Anything else we need to know?
The client that remains on the dashboard after being disconnected for a long time(over 12 hours)
all my clients are configured in same clean_start = true and Session-Expiry-Interval to 0,
These connections that cannot be successfully cleared have strange protocols
Version 5.0.21 is quite old, and it was the first minor version to include replicant support. We've merged several replicant-related bugfixes and improvements after that.
Is this issue also reproducible on more recent EMQX versions, like 5.5, 5.4, etc.?
What happened?
same issure as #12177
but my clients are already set clean_start = true and Session-Expiry-Interval to 0,
but connections still can not remove by it self
What did you expect to happen?
After all connections are disconnected, the dashboard displays 0 connections
How can we reproduce it (as minimally and precisely as possible)?
The error appeared by letting the cluster run for more than one day and connecting / disconnecting a large amount of client, during this period, one core node was restarted once
Anything else we need to know?
The client that remains on the dashboard after being disconnected for a long time(over 12 hours)
all my clients are configured in same clean_start = true and Session-Expiry-Interval to 0,
These connections that cannot be successfully cleared have strange protocols
EMQX version
OS version
Log files
The text was updated successfully, but these errors were encountered: