Skip to content

Job Manager

The job here refers to the long tasks running at the storage layer. For example, compact and flush. The manager means to manage the jobs. For example, you can run, show, stop and recover jobs.

Statements List

SUBMIT JOB COMPACT

The SUBMIT JOB COMPACT command triggers the long-term RocksDB compact operation. The example returns the results as follows:

nebula> SUBMIT JOB COMPACT;
==============
| New Job Id |
==============
| 40         |
--------------

See here to modify the default compact thread number.

SUBMIT JOB FLUSH

The SUBMIT JOB FLUSH command writes the RocksDB memfile in memory to the hard disk.

nebula> SUBMIT JOB FLUSH;
==============
| New Job Id |
==============
| 2          |
--------------

SHOW JOB

List Single Job Information

The SHOW JOB <job_id> statement shows a job with certain ID and all its tasks. After a job arrives to Meta, Meta will split the job to tasks, and send them to storage.

nebula> SHOW JOB 40
==================================================================================================
| Job Id(TaskId) | Command(Dest)              | Status   | Start Time        | Stop Time         |
==================================================================================================
| 40             | flush basketballplayer     | finished | 12/17/19 17:21:30 | 12/17/19 17:21:30 |
--------------------------------------------------------------------------------------------------
| 40-0           | 192.168.8.5                | finished | 12/17/19 17:21:30 | 12/17/19 17:21:30 |
--------------------------------------------------------------------------------------------------

The above statement returns one to multiple rows, which is determined by the storaged number where the space is located.

What's in the returned results:

  • 40 is the job ID
  • flush basketballplayer indicates that a flush operation is performed on space basketballplayer
  • finished is the job status, which indicates that the job execution is finished and successful. Other job status are Queue, running, failed and stopped
  • 12/17/19 17:21:30 is the start time, which is initially empty(Queue). The value is set if and only if the job status is running.
  • 12/17/19 17:21:30 is the stop time, which is empty when the job status is Queue or running. The value is set when the job status is finished, failed and stopped
  • 40-0 indicated that the job ID is 40, the task ID is 0
  • 192.168.8.5 shows which machine the job is running on
  • finished is the job status, which indicates that the job execution is finished and successful. Other job status are Queue, running, failed and stopped
  • 12/17/19 17:21:30 is the start time, which can never be empty because the initial status is running
  • 12/17/19 17:21:30 is the end time, which is empty when the job status is running. The value is set when the job status is finished, failed and stopped

NOTE: There are five job states, i.e. QUEUE, RUNNING, FINISHED, FAILED, STOPPED. Status switching is described below:

Queue -- running -- finished -- removed
     \          \                /
      \          \ -- failed -- /
       \          \            /
        \ ---------- stopped -/

List All Jobs

The SHOW JOBS statement lists all the jobs that are not expired. The default job expiration time is one week. You can change it with meta flag job_expired_secs.

nebula> SHOW JOBS
=============================================================================
| Job Id | Command       | Status   | Start Time        | Stop Time         |
=============================================================================
| 22     | flush test2   | failed   | 12/06/19 14:46:22 | 12/06/19 14:46:22 |
-----------------------------------------------------------------------------
| 23     | compact test2 | stopped  | 12/06/19 15:07:09 | 12/06/19 15:07:33 |
-----------------------------------------------------------------------------
| 24     | compact test2 | stopped  | 12/06/19 15:07:11 | 12/06/19 15:07:20 |
-----------------------------------------------------------------------------
| 25     | compact test2 | stopped  | 12/06/19 15:07:13 | 12/06/19 15:07:24 |
-----------------------------------------------------------------------------

For details on the returned results, please refer to the previous section List Single Job Information.

STOP JOB

The STOP JOB statement stops jobs that are not finished.

nebula> STOP JOB 22
=========================
| STOP Result         |
=========================
| stop 1 jobs 2 tasks |
-------------------------

RECOVER JOB

The RECOVER JOB statement re-executes the failed jobs and returns the number of the recovered jobs.

nebula> RECOVER JOB
=====================
| Recovered job num |
=====================
| 5 job recovered   |
---------------------

FAQ

SUBMIT JOB uses HTTP port. Please check if the HTTP ports among the storages are normal. You can use the following command to debug.

curl "http://{storaged-ip}:12000/admin?space={test}&op=compact"
Last update: April 16, 2021