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

[Dashboard] Replicant Connection Number is Wrongly Displayed #12680

Closed
Estheriii opened this issue Mar 12, 2024 · 1 comment
Closed

[Dashboard] Replicant Connection Number is Wrongly Displayed #12680

Estheriii opened this issue Mar 12, 2024 · 1 comment
Assignees

Comments

@Estheriii
Copy link

Estheriii commented Mar 12, 2024

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?

截图 2024-03-12 11-16-32
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

sysdescr  : EMQX
version   : 5.0.21-g921ce502
datetime  : 2024-03-12T03:19:35.928067136+00:00
uptime    : 18 hours, 19 minutes, 56 seconds

OS version

# On Linux:
$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
$ uname -a
Linux replica-cluster-bb49df858-gd2l7 4.15.0-171-generic #180-Ubuntu SMP Wed Mar 2 17:25:05 UTC 2022 x86_64 GNU/Linux

Log files

@Estheriii Estheriii added the BUG label Mar 12, 2024
@ieQu1 ieQu1 self-assigned this Mar 12, 2024
@ieQu1
Copy link
Member

ieQu1 commented Mar 12, 2024

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.?

@ieQu1 ieQu1 closed this as not planned Won't fix, can't repro, duplicate, stale May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants