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
Hi there,
my group has developed a MQTT server over a Kubernetes cluster. The actual service is reachable through a LoadBalancer that manage 2 pods of the same instance.
The service seems to work pretty well in performance's terms, but there are some strange numbers that we can't understand:
Using MQTT Explorer, we found 2 different sub-topics ID related to aedes-stats:
in the first one, seems to be reported the correct number of connected devices and "maximum" clients connected
the second one, instead, report a a slightly different number of connected clients, but the "maximum"clients seems to report something like "x2" of the first ID report
Is it possible that aedes-stats of the second sub-topic ( that presumably is the second pod of our cluster ) is reporting the "sum" of both "stats" ?
Tnx
The text was updated successfully, but these errors were encountered:
Hi there,
my group has developed a MQTT server over a Kubernetes cluster. The actual service is reachable through a LoadBalancer that manage 2 pods of the same instance.
The service seems to work pretty well in performance's terms, but there are some strange numbers that we can't understand:
image
Using MQTT Explorer, we found 2 different sub-topics ID related to aedes-stats:
in the first one, seems to be reported the correct number of connected devices and "maximum" clients connected
the second one, instead, report a a slightly different number of connected clients, but the "maximum"clients seems to report something like "x2" of the first ID report
Is it possible that aedes-stats of the second sub-topic ( that presumably is the second pod of our cluster ) is reporting the "sum" of both "stats" ?
Tnx
The text was updated successfully, but these errors were encountered: