Opened 3 months ago

Last modified 7 weeks ago

#28224 new defect

Monitor dirauth running sbws in production

Reported by: juga Owned by:
Priority: Medium Milestone: sbws: 1.1.x-final
Component: Core Tor/sbws Version:
Severity: Normal Keywords: sbws-1.0-must-moved-20181128
Cc: micah Actual Points:
Parent ID: #27107 Points:
Reviewer: Sponsor:

Description

We will start running sbws in dirauths. We commented that we will do it one by one.
As teor commented, we should monitor network performance and consensus weight.
This ticket is intended to track any issues.

Child Tickets

Change History (19)

comment:1 Changed 3 months ago by juga

Cc: micah added

comment:2 Changed 3 months ago by juga

To check that the bandwidth measurements do not get worst:

Edit: add total consensus weights

Last edited 3 months ago by juga (previous) (diff)

comment:4 Changed 3 months ago by juga

Current number of relays measured by each bwauth: https://consensus-health.torproject.org/#bwauthstatus

comment:5 Changed 3 months ago by nusenu

Tom, will you add longclaw to the bwauth graphs? (so we can see if longclaw's measured relays count remains the lowest or increases over time)
https://consensus-health.torproject.org/graphs.html#bwauthgraphs

comment:6 Changed 3 months ago by tom

Yes I can! Done. (But I only found this ticket by coincidence, best bet is to cc me on it.)

comment:7 Changed 2 months ago by juga

I created #28355 for the notification about longclaw measuring less relays.

comment:8 Changed 2 months ago by juga

In "BWAuth Measured Relays, Past 14 Days" https://consensus-health.torproject.org/graphs.html#bwauthgraphs, longclaw started going down because of it didn't have raw measurements for the 5th and the 6th. It should go up again in some hours.

Edit: typo

Last edited 2 months ago by juga (previous) (diff)

comment:9 Changed 2 months ago by starlight

longclaw BW scanner started printed broken vote sets with under 1700 relays as of the time of this entry

https://lists.torproject.org/pipermail/tor-consensus-health/2018-November/009378.html

comment:10 Changed 2 months ago by juga

that's because we didn't wait enough to get enough data to start using it in the consensus

comment:11 Changed 2 months ago by starlight

shouldn't it correctly decide when to start publishing automatically?

comment:12 Changed 8 weeks ago by juga

i don't think that dirauth tor code checks how many relays are in the bandwidth file

comment:13 in reply to:  11 Changed 8 weeks ago by teor

Replying to starlight:

shouldn't it correctly decide when to start publishing automatically?

The latest version of sbws only publishes a bandwidth file with relays when it has measured 60% of the network.

comment:14 Changed 8 weeks ago by teor

Component: Core Tor/DirAuthCore Tor/sbws
Milestone: sbws 1.1sbws 1.0 (MVP must)

This is a sbws ticket

comment:15 Changed 7 weeks ago by juga

After several days, most of the circuits timeout. Opened #28639 for this.

comment:16 Changed 7 weeks ago by teor

Keywords: sbws-1.0-must-moved-20181128 added
Milestone: sbws 1.0 (MVP must)sbws 1.0.4

Moving all sbws 1.0 must planning and feature tickets to 1.0.4.

comment:17 Changed 7 weeks ago by teor

Milestone: sbws 1.0.4sbws 1.1

Milestone renamed

comment:18 Changed 7 weeks ago by teor

Milestone: sbws 1.1sbws: 1.1.x

Milestone renamed

comment:19 Changed 7 weeks ago by teor

Milestone: sbws: 1.1.xsbws: 1.1.x-final

Milestone renamed

Note: See TracTickets for help on using tickets.