-
Notifications
You must be signed in to change notification settings - Fork 92
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
Peers update #4
Comments
Hi Audigué, I went through the UDP code, the server will have a timeout
interval of 10000ms for your case which will be the delay after receiving a
ping at which the stale host Handler will mark the host stale. If the next
ping comes fine, after 5 seconds it should work as expected since the
handler is reset.
So my guess is that you need to debug in the
UdpBroadcastService.BroadcastHandler.broadcast( ) code - there are two
unhandled catch blocks and the interfaces enumeration which is where you
might want to start.
Also, is this coming only after scanning for a long time or is there a good
way I can try to reproduce this scenario?
|
Thank's for your response. The "problem" is not with a long scan period it can occur the whenever. |
That's bad! I'll, in all hope, take a look on Sunday
|
Any progress on this issue? |
o dang, never looked into this :| one guess, just by going through this thread, is that the ping alarms that must be set by the system are not accurate alarms but approximate. So if you are looking/discovering for long, these random deviations might add up to significant enough deviations to skip an interval. |
Hello,
I make a long scan (many hours) and the ping is every 5000ms.
Sometimes i have 0 peers connected sometimes 1 and that chnage evry 2-3 times ping.
What are the possibilities that occur ?
Thank's
The text was updated successfully, but these errors were encountered: