Opened 3 years ago

Closed 3 years ago

#21438 closed task (fixed)

retire orestis

Reported by: karsten Owned by: tpa
Priority: Medium Milestone:
Component: Internal Services/Tor Sysadmin Team Version:
Severity: Normal Keywords:
Cc: metrics-team, ln5 Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

It looks like the new Onionoo host orestis has too slow I/O for the background update process. That process is supposed to run once per hour but takes up to 1.5 hours on orestis:

2017-02-11 08:16:04,808 DEBUG o.t.o.cron.Main:147 Started update ...
2017-02-11 10:02:23,439 INFO o.t.o.cron.Main:230 Done.
2017-02-11 10:02:23,439 DEBUG o.t.o.cron.Main:147 Started update ...
2017-02-11 11:22:18,326 INFO o.t.o.cron.Main:230 Done.
2017-02-11 11:22:18,326 DEBUG o.t.o.cron.Main:147 Started update ...
2017-02-11 12:48:30,872 INFO o.t.o.cron.Main:230 Done.
2017-02-11 12:48:30,872 DEBUG o.t.o.cron.Main:147 Started update ...
2017-02-11 14:19:26,622 INFO o.t.o.cron.Main:230 Done.
2017-02-11 14:19:26,622 DEBUG o.t.o.cron.Main:147 Started update ...

The same background update process runs for about 25 minutes on omeiense:

2017-02-11 11:15:11,391 DEBUG o.t.o.cron.Main:147 Started update ...
2017-02-11 11:39:53,571 INFO o.t.o.cron.Main:230 Done.
2017-02-11 12:15:11,391 DEBUG o.t.o.cron.Main:147 Started update ...
2017-02-11 12:40:25,127 INFO o.t.o.cron.Main:230 Done.
2017-02-11 13:15:11,391 DEBUG o.t.o.cron.Main:147 Started update ...
2017-02-11 13:39:43,664 INFO o.t.o.cron.Main:230 Done.
2017-02-11 14:15:11,391 DEBUG o.t.o.cron.Main:147 Started update ...
2017-02-11 14:41:59,334 INFO o.t.o.cron.Main:230 Done.
2017-02-11 15:15:11,391 DEBUG o.t.o.cron.Main:147 Started update ...

If you can, please confirm that I/O is really the issue here. And if so, can you move orestis to a host with faster I/O similar to that of omeiense? Thanks!

Child Tickets

Change History (3)

comment:1 Changed 3 years ago by karsten

Cc: ln5 added

Still too slow for hourly updates, even after the tweaking:

2017-02-21 01:00:38,724 DEBUG o.t.o.cron.Main:147 Started update ...
2017-02-21 02:24:21,800 INFO o.t.o.cron.Main:230 Done.
2017-02-21 02:24:21,800 DEBUG o.t.o.cron.Main:147 Started update ...
2017-02-21 03:39:38,214 INFO o.t.o.cron.Main:230 Done.
2017-02-21 03:39:38,215 DEBUG o.t.o.cron.Main:147 Started update ...
2017-02-21 05:04:58,713 INFO o.t.o.cron.Main:230 Done.
2017-02-21 05:04:58,713 DEBUG o.t.o.cron.Main:147 Started update ...
2017-02-21 06:30:39,784 INFO o.t.o.cron.Main:230 Done.
2017-02-21 06:30:39,785 DEBUG o.t.o.cron.Main:147 Started update ...
2017-02-21 07:59:45,629 INFO o.t.o.cron.Main:230 Done.

I'd say let's give up on orestis and look out for an alternative. Sorry this didn't work out, but thanks for trying!

comment:2 Changed 3 years ago by weasel

Summary: Please move orestis to a host with faster I/Oretire orestis

Ok, we'll kill off orestis then. Pitty.

comment:3 Changed 3 years ago by weasel

Resolution: fixed
Status: newclosed

the new orestis now is just an ssl terminating caching frontend

Note: See TracTickets for help on using tickets.