Opened 6 weeks ago

Last modified 4 weeks ago

#30735 new task

Work out which relays are ignored by all sbws instances

Reported by: teor Owned by:
Priority: Very High Milestone: sbws: 1.1.x-final
Component: Core Tor/sbws Version:
Severity: Critical Keywords: must-keep-3-torflow-blocker, sbws-majority-blocker
Cc: juga Actual Points:
Parent ID: Points: 2
Reviewer: Sponsor:

Description

We need to find out if sbws is excluding any relays.

If the number of excluded relays is small, we can go below 3 torflow instances.

Child Tickets

Change History (3)

comment:1 in reply to:  description ; Changed 5 weeks ago by juga

Replying to teor:

We need to find out if sbws is excluding any relays.

If the number of excluded relays is small, we can go below 3 torflow instances.

Respect to what?, i can think of:

  • number of relays that are in the last consensus (currently 7478)
  • number of relays for which sbws gets the last descriptor (currently 6571)
  • number of relays measured by torflow

comment:2 Changed 5 weeks ago by juga

Ah, i realize now about the detail "by all sbws instances", so are you thinking on a script that would take the relays from the consensus and see which are missing in both longclaw and bastet?, in the bandwidth files for how long?.

comment:3 in reply to:  1 Changed 4 weeks ago by teor

Replying to juga:

Replying to teor:

We need to find out if sbws is excluding any relays.

If the number of excluded relays is small, we can go below 3 torflow instances.

Respect to what?, i can think of:

  • number of relays that are in the last consensus (currently 7478)
  • yes, let's compare with the consensus
    • number of relays for which sbws gets the last descriptor (currently 6571)
  • if we fix bug #30733, then sbws should get all the descriptors, so we won't need this comparison
    • number of relays measured by torflow
  • yes, let's also compare with torflow
  • sbws ignores relays unless they are in the most recent consensus that it has, so it will have a lot fewer relays than torflow
  • we can fix this issue by fixing #30727
Version 0, edited 4 weeks ago by teor (next)
Note: See TracTickets for help on using tickets.