tahoe-lafs/trac-2024-07-25

reduce number of active connections: connect-on-demand #444

New issue

Open

opened 2008-06-03 04:55:37 +00:00 by warner · 1 comment

warner commented

2008-06-03 04:55:37 +00:00

Owner

Eventually, we'll probably need to move away from the current fully-connected-mesh network and do something that will scale better. One point that we discussed was "live != connected-to-introducer, connect on demand". I think this meant that clients don't have to be connected to the introducer to be considered alive (which we've already accomplished), and that we should hold of making a connection to a storage server until we need to, and that we should drop connections when we have too many.

I'm not sure if those will work very well, but this ticket is here to remind us that our roadmap.txt used to have this issue as Connection Management step 3. (step 4 is decentralized introduction: #68, and step5 is relay)

Eventually, we'll probably need to move away from the current fully-connected-mesh network and do something that will scale better. One point that we discussed was "live != connected-to-introducer, connect on demand". I think this meant that clients don't have to be connected to the introducer to be considered alive (which we've already accomplished), and that we should hold of making a connection to a storage server until we need to, and that we should drop connections when we have too many. I'm not sure if those will work very well, but this ticket is here to remind us that our roadmap.txt used to have this issue as Connection Management step 3. (step 4 is decentralized introduction: #68, and step5 is relay)

tahoe-lafs added the

labels 2008-06-03 04:55:37 +00:00

tahoe-lafs added this to the undecided milestone 2008-06-03 04:55:37 +00:00

davidsarah commented

2010-01-16 00:09:20 +00:00

Author

Owner

If you like this ticket, you might like #235 (scale up to many nodes).

If you like this ticket, you might like #235 (scale up to many nodes).

Sign in to join this conversation.

No labels

LeastAuthority.com automation

cannot reproduce

code-frontend-cli

code-frontend-ftp-sftp

code-frontend-magic-folder

code-frontend-web

code-peerselection

dev-infrastructure

somebody else's problem

was already fixed

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#444

No description provided.