Opened 5 weeks ago

Last modified 5 weeks ago

#30905 new defect

Maybe monitoring values in the state file should be reset when sbws is restarted

Reported by: juga Owned by:
Priority: Medium Milestone: sbws: 1.1.x-final
Component: Core Tor/sbws Version: sbws: 1.1.0
Severity: Normal Keywords:
Cc: juga Actual Points:
Parent ID: Points: 1
Reviewer: Sponsor:

Description

I think the following keys should probably be restarted, to make less confusing what appears in the bandwidth file. For instance, after restarting longclaw's sbws, this is what the state file contains, consensus count and priority lists are reset, but not the others:

    "recent_measurement_attempt_count": 671,
    "recent_consensus_count": 1,
    "recent_priority_relay_count": 984,
    "recent_priority_list_count": 3,
    "min_perc_reached": "2019-05-06T06:20:49",

Child Tickets

Change History (2)

comment:1 Changed 5 weeks ago by teor

Milestone: sbws: unspecified → sbws: 1.1.x-final

Yes, this is a bug we should fix in 1.1.0, but it is not a blocker.

We should only do it if we need accurate statistics to fix one of the blockers.

comment:2 Changed 5 weeks ago by teor

Maybe these keys should only include measurements from the last 5 days?

Note: See TracTickets for help on using tickets.