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

Expire dmsg clients from dmsg-discovery entries ; hourly re-registration of dmsg clients #247

Closed
0pcom opened this issue Dec 31, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@0pcom
Copy link
Collaborator

0pcom commented Dec 31, 2023

Counting the number of entries in dmsg-discovery:
https://dmsgd.skywire.skycoin.com/dmsg-discovery/entries

$ curl -L https://dmsgd.skywire.skycoin.com/dmsg-discovery/entries | awk -F "," '{print NF-1}'
10700

There are 10700 dmsg client entries in dmsg-discovery.

Counting the number of visors online:

$ skywire-cli ut -os
3300 visors online

While it's not impossible that we have twice the number of dmsg clients as visors online, it's highly unlikely that this is the case

On checking that dmsg client entries are removed after dmsgcurl, it seems that they are removed appropriately on clean exit.

Solution

  • Expire dmsg client entries from dmsg-discovery after 1 hour.

  • Long-lived dmsg clients should re-register or refresh their entry in dmsg-discovery hourly by some mechanism.

Related issues:

skycoin/skywire-services#38
https://github.com/skycoin/skywire-service-discovery/issues/1
skycoin/skywire#1715

@0pcom 0pcom added the bug Something isn't working label Dec 31, 2023
@mrpalide
Copy link
Contributor

As re-register (heartbeat) logic is expensive, we run dmsg-monitor.
Also we will have new/improve logic on register dmsg clients to discovery that will fix deregister non-visor entries issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants