-
Notifications
You must be signed in to change notification settings - Fork 118
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
TTL on NodeDB[Feature Request]: #445
Comments
Currently when the NodeDB is full the oldest gets removed already. If there are more nodes than fit in the NodeDB, it will always remain full when traffic from other nodes keep coming; this will not be solved with a TTL. Besides, 60 min. would be way too fast for most usage. I do not want to loose my nodes at home when I take my node to work, where I cannot reach them. Also, nodes in Router role have a default periodic broadcast rate as low as 12 hours. |
Platform
ESP32
Description
Currently MQTT nodes lock-up with large node databases. Work around is to soft reset the node and quickly reset NodeDB.
Request to set a TTL on the NodeDB to about 60 minutes (RF and MQTT nodes). If nodes aren't heard within the 60 minutes - They're dropped from the DB.
The text was updated successfully, but these errors were encountered: