[tahoe-dev] [tahoe-lafs] #653: introducer client: connection count is wrong, !VersionedRemoteReference needs EQ
tahoe-lafs
trac at allmydata.org
Fri Jul 17 10:27:02 PDT 2009
#653: introducer client: connection count is wrong, !VersionedRemoteReference
needs EQ
--------------------------+-------------------------------------------------
Reporter: warner | Owner: warner
Type: defect | Status: assigned
Priority: major | Milestone: 1.5.0
Component: code-network | Version: 1.3.0
Keywords: | Launchpad_bug:
--------------------------+-------------------------------------------------
Comment(by warner):
(flogtool note: until we get [http://foolscap.lothar.com/trac/ticket/90
foolscap#90] resolved, you can use "flogtool dump
--verbose" to get the raw seconds-since-epoch timestamps out of the event
logs, which may give you more confidence in comparing them across servers.
There is not yet something similar for "flogtool web-viewer",
unfortunately.
Also note that incident files '''always''' store seconds-since-epoch, so
any
conversion to a string time format is being done by the "flogtool" program
that is processing the incident file)
Yeah, one of the improvements in [3931] was to use a single data structure
to
keep track of storage servers, instead of two separate ones. Seemed more
robust.
I'd have to look more closely at the old code to figure out how
{{{notifyOnDisconnect}}} could be confused. It gets fired when the TCP
connection is lost, so there's no requirement that the remote side
participate in any shutdown-time protocol, but it does get fired through
an
eventual-send, so there could conceivably have been a race condition or
two.
(incidentally, I removed those "Tub.connectorFinished" WEIRD messages in
foolscap-0.4.2, the current release.. they were causing more problems than
they were worth)
--
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/653#comment:13>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid
More information about the tahoe-dev
mailing list