scoreboard server status #1222

Open
opened 2010-10-05 23:54:10 +00:00 by gdt · 0 comments
Owner

Currently, much information is potentially available to a node about the behavior of peers. Every DYHB and share put/fetch tells us something, but this doesn't seem to be stored in an organized way for display/management, and it doesn't seem to be used to deal with a failing server.

This ticket asks for per-server state to be stored about latency and success/failure of various operations, and for it to be displayable in the WUI, perhaps by making each server line a link to a per-server detailed page, and by having a green/yellow/red coloring of each server.

Besides errors, an important item to scoreboard is the server's willingness to take shares. One often sees 12 servers available in the pubgrid, yet 3/7/10 encodings have been unworkable for weeks. Taking shares might be expressible in terms of the range known to work and not work, and probably this should be expressed in advertisements and then scoreboarding can be about failure to honor the advertisement.

Currently, much information is potentially available to a node about the behavior of peers. Every DYHB and share put/fetch tells us something, but this doesn't seem to be stored in an organized way for display/management, and it doesn't seem to be used to deal with a failing server. This ticket asks for per-server state to be stored about latency and success/failure of various operations, and for it to be displayable in the WUI, perhaps by making each server line a link to a per-server detailed page, and by having a green/yellow/red coloring of each server. Besides errors, an important item to scoreboard is the server's willingness to take shares. One often sees 12 servers available in the pubgrid, yet 3/7/10 encodings have been unworkable for weeks. Taking shares might be expressible in terms of the range known to work and not work, and probably this should be expressed in advertisements and then scoreboarding can be about failure to honor the advertisement.
tahoe-lafs added the
code-peerselection
major
enhancement
1.8.0
labels 2010-10-05 23:54:10 +00:00
tahoe-lafs added this to the undecided milestone 2010-10-05 23:54:10 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#1222
No description provided.