#30727: Make sbws vote for all measured relays, even if they are not Running /
not
in the consensus
-------------------------------------------------+-------------------------
Reporter: teor | Owner: (none)
Type: defect | Status: new
Priority: Very High | Milestone: sbws:
| 1.1.x-final
Component: Core Tor/sbws | Version: sbws:
| 1.1.0
Severity: Critical | Resolution:
Keywords: must-keep-3-torflow-blocker, sbws- | Actual Points:
majority-blocker |
Parent ID: #29710 | Points:
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by teor):
Replying to [comment:3 juga]:
> I found more relevant information in
https://trac.torproject.org/projects/tor/ticket/29710?replyto=13#comment:
>
> >
> > sbws only reports bandwidths for Running relays, but torflow reports
bandwidths for all relays it has recently measured.
>
> So, is torflow reporting bandwidth for all the relays seen in the last 5
days even if they were not in the consensus?
Yes.
> What about the relays for which there's no descriptors?, just use the
last descriptor seen?.
Why is sbws missing the descriptors for some relays?
The authorities and directory mirrors should have them?
See bug #30733.
But yes, if we can't get the descriptor in the consensus (or if the relay
is not in the consensus), just use the most recent descriptor data we
have.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30727#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
