10/20/2017 8:41:29 PM
dependencies (#1540)
We recently found Quartz jobs cannot easily inject a dependency. The previously proposal was to add dependencies into Context of Quartz Job. However, it is not recommended, the correct approach is to only inject String or very light weight objects into context. Besides, it increased more complexity for users to leverage Quartz. In this PR, we create a Quartz Job Factory, which is able to seamlessly provide any dependency inside web server.
|
10/13/2017 12:22:29 PM
3.37.0
tests (#1536)
|
10/12/2017 9:22:25 PM
(#1533)
|
|
|
10/12/2017 2:40:44 PM
getting this error in startup:
Exception in thread "main" com.google.inject.ProvisionException: Unable to provision, see the following errors: 1) Error injecting constructor, org.quartz.SchedulerConfigException: Thread count must be > 0 at azkaban.scheduler.QuartzScheduler.<init>(QuartzScheduler.java:52) at azkaban.scheduler.QuartzScheduler.class(QuartzScheduler.java:48) while locating azkaban.scheduler.QuartzScheduler for the 11th parameter of azkaban.webapp.AzkabanWebServer.<init>(AzkabanWebServer.java:161) at azkaban.webapp.AzkabanWebServer.class(AzkabanWebServer.java:119) while locating azkaban.webapp.AzkabanWebServer for the 1st parameter of azkaban.soloserver.AzkabanSingleServer.<init>(AzkabanSingleServer.java:48) while locating azkaban.soloserver.AzkabanSingleServer
|
|
|
10/10/2017 8:45:56 PM
request: #1526
This PR provides skeleton for building dependency check.
Plugin needs to implement two interfaces: DependencyCheck and DependencyInstanceContext for their custom data dependency type.
|
10/10/2017 8:19:51 PM
a problem when a queued job would disappear from the job list view when its state changes to QUEUED.
Currently, you can access job logs for current and failed attempts in the Job List tab of an execution.
If some job failed and has retries, it goes into QUEUED state while sleeping before the next attempt.
If you want to see why any of the previous attempts failed, you can right-click the grey attempt bar
To see how long it's going to sleep, you can check the job log
Without this fix you can't do either of those if the job is sleeping, because it's hidden if the state is QUEUED.
Also if you have a job that hasn't yet started to run but is in QUEUED state (ie. blocked by pipeline), if you want to know why it's queued, you should check the job log. If you can't access the job log via Job List tab, this is not easily accomplished.
|
10/10/2017 5:05:27 PM
PR proposes bringing quartz to AZ. Quartz Scheduler provides 3 modes of job stores: RAMJobStore, JDBCJobStore, and TerraCottaJobStore. In order to persist the job statuses out of Application memory regardless of downtime, we recommend using JDBC JobStore. In fact, users can specify the mode in quartz properties.
This code patch creates Quartz server and manages Quartz API (e.g., start, pause, shut down) at class QuartzScheduler. We directly use h2-in-memory DB to directly test JDBC Quartz in unit test.
|
10/6/2017 3:21:51 PM
add flow_id to key set of execution_jobs table
2. drop two unnecessary indexes.
Previously primary key set of execution_jobs is (execution_id, job_id, attempt).
This is under the assumption where no job shares the same name within a flow. However this is not the case when embedded flow comes into picture, which allows user to embed a smaller flow into multiple places inside a bigger flow.
With new keyset, two indexes becomes a subset of the key set, so we can drop them.
|
