[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #24983 [Metrics/CollecTor]: Inaccessible semi-recent consensus files
#24983: Inaccessible semi-recent consensus files
-------------------------------+--------------------------
Reporter: robgjansen | Owner: karsten
Type: defect | Status: accepted
Priority: Medium | Milestone:
Component: Metrics/CollecTor | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
-------------------------------+--------------------------
Comment (by iwakeh):
Replying to [comment:2 karsten]:
> Yes, this is a known (to me), but probably yet undocumented issue.
Thanks for creating this issue! It bothered me from time to time, but not
enough to open a ticket. ;)
>
> So, making more files available in the `recent/` directory would be one
option. But all tools downloading from that directory would then have to
fetch even more data. I'm thinking of newly bootstrapped Onionoo instances
for development purposes, for one example.
Valid point.
>
> Another option would be to create tarballs for the `archive/` directory
more often. Maybe every 2 days instead of every 3 days. That would solve
this issue, too, right? If so, and if there are no concerns, I'll change
the cronjob to try this out for a week or so.
That should be fine.
(We should keep this in mind when we get around to 'java-ize' the
archiving process.)
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24983#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs