-
Notifications
You must be signed in to change notification settings - Fork 43
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
Dispersy walker has fewer candidates than expected #38
Comments
Option: perhaps the majority of the peers that we contact do not return new peers for some reason? This would explain why we get few candidates while the walk success rate is relatively high. This should be fairly easy to confirm of deny. |
Reproduced this on my Ubuntu machine. |
Ended up being a bug in the tracker. Long story short, the tracker's response messages would use the highest 'community version number' that the tracker knew of. Hence, once someone talked to the trackers using version 0002 it would respond to any subsequent request (from any other peer in that community) with version 0002. This response would then be dropped because this version is unknown. To fix this the tracker code has been modified to only respond with version 0000. All trackers are still running the older svn based code and we will not update svn. Instead, we will fix the code on git and slowly migrate our trackers to the latest git. |
We would expect more candidates sooner. Especially the AllChannelCommunity takes much longer to obtain a good number of candidates than we would expect.
Strangely enough the walk success rate is relatively high (around 80%). This contradicts the lack of available candidates.
This behaviour must be either solved or explained. Please investigate.
The text was updated successfully, but these errors were encountered: