-
Notifications
You must be signed in to change notification settings - Fork 63
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
Retain functionality works inconsistently #109
Comments
"It seems that only 10 messages every get retained, is this a configuration flag" |
@Gujiawei-Edinburgh, in the info log there was the following line: RetainMessageMatchLimit=10, is it possible that this has to do with the reported behavior? seems that this configuration sets the match limit for a retain message topic subscription match? where can we change this config from? How do you find that the message is not retained, e.g by subscribing the topic? No, I am doing a wildcard subscription and i've figured that is the real issue. Bifromq will limit the retained topics matched if its a wildcard subscription based on the RetainMessageLimit config flag. |
@saraheem If your subscribed topic, i.e. topic filter, has wildcard, e.g. * or #, it will match multiple topics. If so, during matching process, if the number of matched topics exceeds the limit which is 10 by default, you cannot get all the retained messages. You can write your own setting provider to override the default settings. |
Version: 3.3.3
Deployment Config: Windows 11, OpenJDK 21.0.5, Standalone mode, Default configuration
Tools: Using Mqtt-Stresser for pub/sub
A Steps:
Behavior:
No message being retained.
B Steps:
Behavior:
Only 10 topics are retained and the rest do not get retained
C Steps:
Behavior:
It seems that only 10 messages every get retained, is this a configuration flag
The text was updated successfully, but these errors were encountered: