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
If ThreadDumper wakes up to save to disk periodically, it may miss nodes that are otherwise good and won't save them to disk. This is because it basically is getting nodes to save to disk from CAddrDb from its two lists: ourId and unkId.
However, when the crawler threads run, they "take" IPs to check from the CAddrDb class. These nodes are temporarily "popped" off the internal lists ourId and/or unkId (only to be returned later once a good/bad result is determined by the crawler).
So if ThreadDumper wakes up while any crawlers are actively checking nodes.. those nodes won't get saved to disk. :'(
The text was updated successfully, but these errors were encountered:
If
ThreadDumper
wakes up to save to disk periodically, it may miss nodes that are otherwise good and won't save them to disk. This is because it basically is getting nodes to save to disk fromCAddrDb
from its two lists:ourId
andunkId
.However, when the crawler threads run, they "take" IPs to check from the
CAddrDb
class. These nodes are temporarily "popped" off the internal listsourId
and/orunkId
(only to be returned later once a good/bad result is determined by the crawler).So if
ThreadDumper
wakes up while any crawlers are actively checking nodes.. those nodes won't get saved to disk. :'(The text was updated successfully, but these errors were encountered: