#29258: Provide an IPv6 address for the Snowflake broker --------------------------------------------+------------------------------ Reporter: ahf | Owner: dcf Type: task | Status: merge_ready Priority: Medium | Milestone: Component: Circumvention/Snowflake | Version: Severity: Normal | Resolution: Keywords: anti-censorship-roadmap-august | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: | Sponsor28-must --------------------------------------------+------------------------------ Changes (by cohosh):
* status: needs_review => merge_ready Comment: Okay I think we can go ahead and finish switching hosts now. >About logs, I'm thinking we just let the log files happen in parallel on the old and new hosts. Then after we've made the switch, we check the old logs for sanitization and publish them. Logs we publish in the future from the new broker will partially temporally overlap those from the old, but that should be no problem. The metrics logs will be the largest problem (see #322131). I propose this for the switch: - stop the broker process on the new and old host - copy over all metrics log files from the old host to the new host - start the new host We're going to lose partial metrics for the collection period that overlaps with the switch, but that actually happens every time we restart the broker since metrics for the time period (which is one) are stored in memory until the time period ends at which point they are written to a file. So, maybe the better question to ask here is: is that okay and if not how do we solve it more generally? -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/29258#comment:15> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs