Treasure Data has a scheduler feature that supports periodic query execution. We take great care in distributing and operating our scheduler in order to achieve high availability. By using this feature, you no longer need a cron daemon on your local datacenter.

Prerequisites

• Basic knowledge of Treasure Data, including the toolbelt.
• A table with some data. An example is provided in the Getting Started guide.

Create the Schedule

A new schedule can be created using the td sched:create command. The name of the schedule, cron-style schedule, query, and the database name are required.

$ td sched:create \
  hourly_count \
  "0 * * * *" \
  "select count(1) from www_access" \
  -d testdb

Scheduled jobs must sometimes be set as high priority items. The -P option is used to specify the priority. The priority is between -2 (VERY LOW) and 2 (VERY HIGH), where 0 is the default. The priority can be changed later using td sched:update -P.

# VERY HIGH
$ td sched:create -P  2 ...
# NORMAL (Default)
$ td sched:create -P  0 ...
# VERY LOW
$ td sched:create -P -2 ...

List the Schedules

You can see the list of currently scheduled entries by td sched:list.

$ td sched:list
+--------------+-----------+----------+---------------------------+-------+--------+----------+---------------------------------+
| Name         | Cron      | Timezone | Next schedule             | Delay | Result | Database | Query                           |
+--------------+-----------+----------+---------------------------+-------+--------+----------+---------------------------------+
| hourly_count | 0 * * * * | UTC      | 2012-06-12 12:00:00 -0700 | 0     |        | testdb   | select count(1) from www_access |
+--------------+-----------+----------+---------------------------+-------+--------+----------+---------------------------------+

Show the History of Schedules

td sched:history shows the job history of a schedule entry. To investigate the results of each individual job, please use td job <jobid>.

$ td sched:history hourly_count
Name         : hourly_count
Cron         : 0 * * * *
Timezone     : UTC
Delay        : 0 sec
Next         : 2012-06-12 19:00:00 UTC
Result       : 
Database     : testdb
Query        : select count(1) from www_access
+--------+---------------------------+---------+--------+
| JobID  | Time                      | Status  | Result |
+--------+---------------------------+---------+--------+
| 371336 | 2012-06-12 11:00:00 -0700 | success |        |
| 371242 | 2012-06-12 10:00:00 -0700 | success |        |
| 371147 | 2012-06-12 09:00:00 -0700 | success |        |
| 371048 | 2012-06-12 08:00:00 -0700 | success |        |
| 370973 | 2012-06-12 07:00:00 -0700 | success |        |
| 370900 | 2012-06-12 06:00:00 -0700 | success |        |
| 370823 | 2012-06-12 05:00:00 -0700 | success |        |
| 370718 | 2012-06-12 04:00:00 -0700 | success |        |
| 370610 | 2012-06-12 03:00:00 -0700 | success |        |
| 370515 | 2012-06-12 02:00:00 -0700 | success |        |
| 370333 | 2012-06-12 01:00:00 -0700 | success |        |
| 370162 | 2012-06-12 00:00:00 -0700 | success |        |
| 370077 | 2012-06-11 23:00:00 -0700 | success |        |
| 369954 | 2012-06-11 22:00:00 -0700 | success |        |
| 369790 | 2012-06-11 21:00:00 -0700 | success |        |
| 369651 | 2012-06-11 20:00:00 -0700 | success |        |
| 369526 | 2012-06-11 19:00:00 -0700 | success |        |
| 369449 | 2012-06-11 18:00:00 -0700 | success |        |
| 369329 | 2012-06-11 17:00:00 -0700 | success |        |
| 369284 | 2012-06-11 16:00:00 -0700 | success |        |
+--------+---------------------------+---------+--------+
20 rows in set

Delete the Schedule

td sched:delete will remove the schedule.

$ td sched:delete hourly_count

If this article is incorrect or outdated, or omits critical information, please let us know. For all other issues, please see our support channels. Live chat with our staffs also work well.