Some Entries in the Job view do not have Dag Ids

[r39132]

Here are the Dags that I have!

However, I see some running in the job view that do not have dag ids!

I am running code synced via Git from master -- last sycned on Friday, July 17th, 5pm PST.

[mistercrunch]

The jobs are used for anything that derives BaseJob (SchedulerJob, BackfillJob, LocalTaskJob, ...).

I think when you CTRL-C kill the scheduler, it may leave a "RUNNING" entry in the DB.

I'm not sure what job id 14 is about...

[r39132]

I have been 'CTRL-C'ing the scheduler very liberally -- I should SIGTERM it, assuming that the processes catch that signal and terminate cleanly, including cleaning up the DB of any running jobs on those processes? Asked another way, what is the correct way to terminate the scheduler and or backfill jobs so that they do not leave tasks in the running state forever?

In my "monit" automation, I am SIGTERM'ing both the webserver and scheduler processes, so assume that is the clean way to shutdown.

[r39132]

We are using the LocalScheduler, so I am guessing those tasks are running as LocalTaskJobs. This turned out to be one of our model building jobs.

[r39132]

But, to my original question, isn't dag_id required? Why would it be empty? I guess I'm asking whether this is a bug. In my case, I have not subclassed BaseJob, so the fact that the job view is not displaying dag_ids seems like a bug.

[mistercrunch]

It's expected that SchedulerJob instances would have an empty dag_id column.