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
I see a cons of current gossip method is the client is trying connect inbox/outbox relays before query event
// Add outbox relaysfor url in broken_down.outbox_urls.into_iter(){ifself.add_outbox_relay(&url).await? {self.connect_relay(url).await?;}}// Add inbox relaysfor url in broken_down.inbox_urls.into_iter(){ifself.add_inbox_relay(&url).await? {self.connect_relay(url).await?;}}
If relay have some errors, client will try reconnect, the fetch events will become very slow. I wonder if when this issue is resolved (gossip storage and relays rank/score implemented). Will this problem be solved too?
If relay have some errors, client will try reconnect, the fetch events will become very slow.
Yes, this is true but after few attempts the SDK will start skipping unresponsive relays (this in general, not only for gossip). This require some secs so if the relay was just added it will not be skipped.
I wonder if when this issue is resolved (gossip storage and relays rank/score implemented). Will this problem be solved too?
Yeah, partially. I still have to study the best way to implement it. Using a relay score I can ignore the unresponsive relays but for new ones the issue could still persist (if the relays are new, never saw before).
The text was updated successfully, but these errors were encountered: