Opened 8 years ago

Closed 7 years ago

#5504 closed defect (fixed)

Consensus archive tarballs do not contain any consensuses produced at xx:30

Reported by: rransom Owned by:
Priority: Low Milestone:
Component: Metrics/CollecTor Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

When the dirauths have failed to produce a consensus for some period of time, they start trying to produce consensuses at half-hour intervals. They have done that at least twice since the beginning of 2011, but the consensus tarballs for that period do not contain any consensuses produced at xx:30.

Child Tickets

Change History (3)

comment:1 Changed 8 years ago by karsten

Priority: normalminor

Yes, this would be useful to have. It's more complicated to implement than it should be, though. metrics-db is run in an hourly cronjob. And it sometimes takes a good fraction of that hour. We'd have to decouple a few more things to run only the consensus (and vote) download twice an hour.

As a quick fix I just set up a second instance of metrics-db that runs at :45 and downloads whatever consensuses and votes it gets. If it finds a consensus that wasn't published at :00 of an hour, it sends me mail and I'll copy files over to the main metrics-db instance to get them included in the tarballs. If it happens twice per year, that should be fine. In the long-term we should have a real fix though. Reducing priority to minor, now that we have at least a workaround.

comment:2 Changed 8 years ago by Sebastian

It happens whenever we failed to make a consensus, and the next time we succeed happens to be at a half-hour.

comment:3 Changed 7 years ago by karsten

Resolution: fixed
Status: newclosed

Decoupled the metrics-db code and improved its performance so that two runs per hour are possible now. Changing the cronjob to run at :05 and :35. Closing.

Note: See TracTickets for help on using tickets.