> > > Primarily the fact that the graphical representation of it (under > "Routing > > > table" or on the "Node Reference Status" page), instead of looking nice > > and > > > healthy with plenty of routing 'knowledge' (resembling a barcode), > starts > > off > > > almost completely white with just a handful of thin stripes. Over a day > or > > > so, coverage increases. > > > > Same over here.... Cannot tell for sure that it happens every time I > restart > > but I definitely has seen the 'barcode' cleared when the node is freshly > > started. > > I can now say that it definitely not happens every time...We'll see if I can > provoke it to happen again..
One thing that happens though is that is seems to appear a lot of new (old really) nodes in the routing table during a restart. After a restart after 10 hrs of uptime the version histogram looks something like: Fred,0.4,1.46,522 |= Fred,0.5,1.46,5007 |= Fred,0.5,1.46,5009 |= Fred,0.5,1.46,5010 |== Fred,0.5,1.46,5012 |== Fred,0.5,1.46,5014 |==== Fred,0.5,1.46,5015 |============ Fred,0.5,1.46,5017 |========== Fred,0.5,1.46,5018 |======== Fred,0.5,1.46,534 |= Fred,0.5,1.46,567 |= Fred,0.5,1.46,568 |= Fred,0.5,1.46,570 |= Fred,0.5,1.46,571 |= Fred,0.5,1.46,572 |== Fred,0.5,1.46,598 |= Fred,0.6,1.46,6119 |= And I remember looking at it right before restart and thinking 'whoa, seems to be only 50xx nodes in the network nowadays'.. The, after the node has been running for an hour or so the version histogram looks like: Fred,0.5,1.46,5004 |= Fred,0.5,1.46,5007 |= Fred,0.5,1.46,5009 |= Fred,0.5,1.46,5010 |== Fred,0.5,1.46,5012 |= Fred,0.5,1.46,5014 |=== Fred,0.5,1.46,5015 |============= Fred,0.5,1.46,5017 |========= Fred,0.5,1.46,5018 |================ Fred,0.6,1.46,6122 |= Fred,0.6,1.46,6508 |= At that point I restarted the node and again there magically appeared bunch of old-versioned nodes in the rt (I have seen larger mutations than this happen though.. maybe the mutation level is a product of uptime in some way..) Fred,0.4,1.46,519 |= Fred,0.5,1.46,5007 |= Fred,0.5,1.46,5009 |= Fred,0.5,1.46,5010 |== Fred,0.5,1.46,5012 |= Fred,0.5,1.46,5014 |=== Fred,0.5,1.46,5015 |============ Fred,0.5,1.46,5017 |========= Fred,0.5,1.46,5018 |=============== Fred,0.5,1.46,545 |= Fred,0.5,1.46,563 |= Fred,0.5,1.46,598 |= Fred,0.6,1.46,6508 |= There is also an awful lot of orphaned properties being removed during rt initialization. I have seen 449 properties beeing reduced to 98, 170 down to 90 and 119 down to 100. The initial number (449 etc) seems to be tightly related to my node:s uptime. The 449 props where from 48 hrs of uptime, the 170 from 10 hrs and 119 from 1 hour. Isn't this the bulk of my node:s routing knowledge beeing removed? I have not yet looked into the code much to try to figure out the cause of these odd behaviours but I remember something from a release notification from quite a while back about 'selecting a random set of seednodes from seednodes.ref', could that be related to this in some way (a quick glance at the code hints that it isn't so, but still it would be good to get some confirmation on this from someone)? Could someone do a similar test with their node to rule out that I am the only one that this happens to. To see how many properties that are removed when you restart you can count the number of '(freenet.node.rt.DataObjectRoutingStore, main, NORMAL): Removing orphaned property.....' rows written to the log during node startup. I will not be able to look into this for a couple of days since I am going for a weekend vacation later today. /N _______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
