|
|
3/23/2017 8:18:54 PM
shutdown API is called. (#947)
When shutdown api is called, executor will deactivate itself, wait for all the job to finish, then call system.exit(), which triggers the shutdown hook. In shutdown hook, executor clears the database entry and forces a shutdown of all active threads.
|
3/22/2017 7:42:56 PM
script was updated with the new shared logic - launch script was refactored - launch script to fail if server already started.
|
|
|
3/20/2017 6:45:27 PM
when executor host is running out of memory (#937)
Currently a job will be killed right away before actual execution if there's not enough memory. But as memory usage fluctuates, it's possible there will be enough memory later. Therefore we should retry the job if memory requirement is not met.
Testing:
Given the nature of this code change, it's difficult to add automated tests. For now we tested the change as by replacing SystemMemoryInfo.canSystemGrantMemory with a function which returns true or false based on given probability, then manually verified it's logging correctly and hitting the according code path.
|
3/16/2017 6:24:51 PM
(#941)
Shutdown the process with kill -9 at the end in shutdown scripts
If all attempts to killing the web server/executor fail to kill the process, we will do a force kill (kill -9).
|
3/16/2017 3:41:29 PM
comments on Jetty Performance metrics
Details what Jetty metrics is doing
|
3/15/2017 6:53:28 PM
(#940)
Creating the azkaban-spi package which is intended to be the contract against different Azkaban modules.
Added a Storage interface and related exception class hierarchy.
|
3/14/2017 7:19:23 PM
bean to parse a yaml spec. Added a unit test to validate a sample spec.
|
3/11/2017 8:28:46 PM
(#863)
The versions currently used are old and have some known security
vulnerabilities (such as CVE-2014-3577 and CVE-2015-5262).
|
