Opened at 2007-06-26T01:18:24Z
Last modified at 2016-09-13T00:50:32Z
#68 closed enhancement
One introducer = single point of failure — at Initial Version
| Reported by: | lvo | Owned by: | somebody |
|---|---|---|---|
| Priority: | major | Milestone: | 1.12.0 |
| Component: | code-network | Version: | 0.2.0 |
| Keywords: | scalability availability introduction gsoc docs anti-censorship test-needed research i2p-collab | Cc: | zooko, killyourtv@…, mmoya@…, K1773R@…, clashthebunny@…, leif@…, skydrome@…, tahoe-lafs-trac@…, tahoe-lafs.org@…, zl29ah@…, vladimir@… |
| Launchpad Bug: |
Description
I am quite sure you are aware of the problem that an introducer/vdrive server crash bringing everything down. I read your roadmap.txt but I didn't find anything specific to address this. May I suggest using introducers.furl and vdrives.furl where multiple entries can be used and the information is updated to all introducers at the same time when a peer makes an update.
Also, upon adding a new introducer, there should be a way to discover all the info currently on the existing introducer. I think I am making this part sounds more trivial than it is.
Thanks Lu
Note: See
TracTickets for help on using
tickets.
