|
Hi all,
I've been doing some heavy testing of fcpputsite on
0.4 (today's CVS), and have hit a severe snag
After inserting about 240 MB worth of 256k
splitfiles, my node goes totally catatonic - It just stops sending back
responses to the outstanding ClientPut messages.
What's strange is that it seems to fail at the same
point every time (give or take about 5MB).
It works perfectly up till that point, then seizes
up abruptly.
More, I repeated the test on a transient node on my
Windows box, and all the inserts, 1GB worth, go through fine.
I had been inserting at htl=3, but always sooner or
later hit a constant stream of RouteNotFound messages, so I cut it to
htl=0.
It is even at htl=0 that I get the problems
described above.
From what I can tell, fcpputsite gets held up
waiting for some kind of response from ClientPut.
Even after hours, no response comes. Not even those
beloved 'Pending' messages.
Also, I've tried a couple of times with a fresh
datastore (created by changing the size in freenet.ini), but the same thing
keeps happening.
I'm wondering if I should build a timeout mechanism
into fcpputsite, so that if a response from ClientPut doesn't come back within
(say) one hour, the thread gets killed and a new thread re-sends the
ClientPut.
Thoughts please?
David
|
