Re: [tor-bugs] #25799 [Metrics]: Utilize all Onionoo instances

[Tor Bug Tracker & Wiki]

#25799: Utilize all Onionoo instances
-+--
 Reporter:  iwakeh   |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by irl):

 We would notice more quickly perhaps. (:

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25799 [Metrics]: Utilize all Onionoo instances

[Tor Bug Tracker & Wiki]

#25799: Utilize all Onionoo instances
-+--
 Reporter:  iwakeh   |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by karsten):

 Replying to [comment:3 irl]:
 > Perhaps the easiest solution is to have Onionoo instances die if their
 data has become stale. We should make sure that in this case, Varnish then
 automatically stops routing requests to that instance and instead routes
 to another live instance (this is not stale).

 While being simple, this solution has a major disadvantage: what if all
 Onionoo instances receive stale data as input and each of them decides for
 itself that they should rather shut down? Hmm.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25799 [Metrics]: Utilize all Onionoo instances

[Tor Bug Tracker & Wiki]

#25799: Utilize all Onionoo instances
-+--
 Reporter:  iwakeh   |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  High |  Milestone:
Component:  Metrics  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by irl):

 Perhaps the easiest solution is to have Onionoo instances die if their
 data has become stale. We should make sure that in this case, Varnish then
 automatically stops routing requests to that instance and instead routes
 to another live instance (this is not stale).

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25799 [Metrics]: Utilize all Onionoo instances

[Tor Bug Tracker & Wiki]

#25799: Utilize all Onionoo instances
-+--
 Reporter:  iwakeh   |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  High |  Milestone:
Component:  Metrics  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by iwakeh):

 Replying to [comment:1 karsten]:
 >...
 >
 > What else could we do? How about we teach Onionoo instances to detect
 when their data has become stale. In that case they could check whether
 other instances have more recent data and reply with redirects to other
 instances until their data is not stale anymore.

 This solution alleviates the admins work load (no additional scripting,
 monitoring etc. on the admin's side).  The necessary configuration
 implementation should pay attention to the decisions made in #24041.
 That's ok.

 Seems like we have an agreement on keeping the solution inside Onionoo
 avoiding pushing the task toward operation?

 If yes, the next steps would be:
 * define the redirect algorithm
 * define the configuration accordingly
 * implement the above.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #25799 [Metrics]: Utilize all Onionoo instances

[Tor Bug Tracker & Wiki]

#25799: Utilize all Onionoo instances
-+--
 Reporter:  iwakeh   |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  High |  Milestone:
Component:  Metrics  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by karsten):

 Wait, I think it's not that the case that RS only requests data from the
 main Onionoo instance. IIUC, onionoo.tpo sometimes goes to omeiense and
 sometimes to oo-hetzner-03. Or rather, it goes to one of the several
 caches which in turn use both backends. The effect is that some requests
 made by RS are answered by the first instance, directly or indirectly, and
 some by the next. This switch may even happen in the middle of a user
 session.

 Regarding your second suggestion to have RS fetch data from several
 instances, I think that wouldn't scale. Remember that it's really the
 clients/browsers making those requests. So, basically, that would double
 the number of requests.

 Regarding your first suggestion, I don't really know how the DNS round-
 robin thing works or how we would change that to detect stale data. It
 might be that this requires some programming/configuration effort, too.

 What else could we do? How about we teach Onionoo instances to detect when
 their data has become stale. In that case they could check whether other
 instances have more recent data and reply with redirects to other
 instances until their data is not stale anymore.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs