[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #25091 [Metrics/Onionoo]: Make 'out/update' deterministic across instances
#25091: Make 'out/update' deterministic across instances
-----------------------------+------------------------------
Reporter: iwakeh | Owner: metrics-team
Type: enhancement | Status: closed
Priority: Medium | Milestone:
Component: Metrics/Onionoo | Version:
Severity: Normal | Resolution: wontfix
Keywords: | Actual Points: 0.1
Parent ID: #25002 | Points:
Reviewer: | Sponsor:
-----------------------------+------------------------------
Changes (by karsten):
* status: new => closed
* resolution: => wontfix
* actualpoints: => 0.1
Comment:
Or let's not do it. I already had a working patch, but then realized that
the timestamp in `out/update` is used for different two purposes: 1) for
`server.NodeIndexer` to quickly check whether there's new data to index
and 2) for the various `writer.*DocumentWriter` to obtain a list of status
files that were written or updated after the last execution. We cannot
simply use the maximum last-seen time as timestamp in the `out/update`
file, or we'd rewrite lots of document files from status files that
haven't changed. We could have two separate files `status/update` and
`out/update` for the two different purposes. But is that really worth the
effort, just to make `out/update` deterministic across instances? I don't
think so. Closing as wontfix.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25091#comment:1>
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