Opened 7 years ago

Last modified 7 months ago

#2715 new enhancement

Is rephist-calculated uptime the right metric for HSDir assignment?

Reported by: arma Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.7
Severity: Normal Keywords: research, tor-dirauth, research-program
Cc: Actual Points:
Parent ID: #16538 Points: medium
Reviewer: Sponsor: SponsorR-can

Description

In #2709 we changed the HSDir flag to be based on each authority's opinion of the relay's uptime, rather than the relay's own opinion of its uptime.

Nick then asked if perhaps WFU would be a better measure. We should consider if there are smarter parameters to consider.

See also #2714.

Child Tickets

Change History (26)

comment:1 Changed 7 years ago by Sebastian

To be a useful hsdir, we need to know how long the relay will stay up once it is started. We don't care how long it is down, and this shouldn't negatively influence our choice.

comment:2 Changed 7 years ago by arma

I think WFU is the wrong metric. What we're looking for is likelihood of staying up for the next n minutes (where n is something we should discover in #2714).

Currently we assume that if you've been up 26 hours, you'll be up a while more. No idea if that assumption is justified. We have the data if somebody wants to look.

Really, the metric we're looking for here is much more akin to MTBF.

comment:3 Changed 7 years ago by nickm

Milestone: Tor: 0.2.3.x-final

comment:4 Changed 6 years ago by nickm

Milestone: Tor: 0.2.3.x-finalTor: 0.2.4.x-final

comment:5 Changed 5 years ago by nickm

Keywords: tor-auth added

comment:6 Changed 5 years ago by nickm

Component: Tor Directory AuthorityTor

comment:7 Changed 5 years ago by nickm

Milestone: Tor: 0.2.4.x-finalTor: 0.2.5.x-final

comment:8 Changed 4 years ago by nickm

Milestone: Tor: 0.2.5.x-finalTor: 0.2.???

comment:9 Changed 3 years ago by arma

Keywords: SponsorR added

comment:10 Changed 3 years ago by arma

Parent ID: #13209

comment:11 Changed 3 years ago by nickm

Milestone: Tor: 0.2.???Tor: 0.2.7.x-final

These may be worth looking at for 0.2.7.

comment:12 Changed 3 years ago by nickm

Status: newassigned

comment:13 Changed 3 years ago by nickm

Keywords: 027-triaged-1-in added

Missed these two.

comment:14 Changed 3 years ago by isabela

Keywords: research added
Points: medium
Version: Tor: 0.2.7

comment:15 Changed 2 years ago by arma

Parent ID: #13209#16538

Is this ticket now redundant with the other children of #16538?

comment:16 Changed 2 years ago by nickm

Milestone: Tor: 0.2.7.x-finalTor: 0.2.8.x-final

comment:17 Changed 2 years ago by nickm

Keywords: SponsorR removed
Sponsor: SponsorR

Bulk-replace SponsorR keyword with SponsorR sponsor field in Tor component.

comment:18 Changed 2 years ago by dgoulet

Keywords: 027-triaged-1-in removed

comment:19 Changed 23 months ago by nickm

Milestone: Tor: 0.2.8.x-finalTor: 0.2.???

It is impossible that we will fix all 252 currently open 028 tickets before 028 releases. Time to move some out. This is my first pass through the "assigned" tickets with no owner, looking for things to move to ???.

If somebody thinks they can get these done before the 0.2.8 timeout, please assign it to yourself and move it back?

comment:20 Changed 21 months ago by dgoulet

Sponsor: SponsorRSponsorR-can

Move those from SponsorR to SponsorR-can.

comment:21 Changed 13 months ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:22 Changed 12 months ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:23 Changed 7 months ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:24 Changed 7 months ago by dgoulet

Keywords: tor-dirauth added; tor-auth removed

Turns out that tor-auth is for directory authority so make it clearer with tor-dirauth

comment:25 Changed 7 months ago by nickm

Keywords: research-program added
Severity: Normal

comment:26 Changed 7 months ago by nickm

Status: assignednew

Change the status of all assigned/accepted Tor tickets with owner="" to "new".

Note: See TracTickets for help on using tickets.