[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #13003 [Onionoo]: Figure out a better strategy to avoid concurrent Onionoo executions

#13003: Figure out a better strategy to avoid concurrent Onionoo executions
-------------------------+-----------------
     Reporter:  karsten  |      Owner:
         Type:  defect   |     Status:  new
     Priority:  normal   |  Milestone:
    Component:  Onionoo  |    Version:
   Resolution:           |   Keywords:
Actual Points:           |  Parent ID:
       Points:           |
-------------------------+-----------------

Comment (by iwakeh):

 I second giving up cron:
 cron is designed for entirely independ executions (ideally).
 Having a long running task and not wanting the next task to run, unless
 the
 previous one is finished introduces a dependency between the two.
 Once there is such a dependency it should rather be addressed by design.

 Some ideas for a different approach:

 * Using the
 [http://docs.oracle.com/javase/7/docs/api/java/util/concurrent/ScheduledExecutorService.html
 ScheduledExecutorService] with fixed rate or delay gives quite some
 control over the single executions and could mail in case of failure.

 * If the future version of onionoo uses logging (e.g. logback), the
 failure mails could be sent via an
 [http://logback.qos.ch/manual/appenders.html#SMTPAppender SMTPAppender].

 * Actually, a combination of these two might be best: java controlled
 timed execution and mailing via SMTPAppender.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13003#comment:3>
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