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).
|
3/10/2017 7:24:28 PM
team recommended version. Build is successful.
|
3/9/2017 2:31:10 AM
(#929)
Check if the process to be killed is dead in shutdown scripts. After killing the process, shutdown scripts check whether the process is dead and retry if not. Shutdown will fail if process is still alive after all retries.
|
3/7/2017 2:46:16 PM
3.16.0
Code Refactor and adding key metrics
This commit adds and fixes the following metrics:
* Flow failure rate
* project zip uploading time duration log
* correct the right NumRunningFlows in web server
* add Jetty thread pool metrics as a Web Server performance monitor
* adding measure DB connection time as a metrics for DB connection pool performance
|
3/2/2017 3:35:10 AM
User can fill in their own alias in property file. It will be used as hostname in getHost(). If not configured we will use canonical hostname as fallback. 2. Put the property name "executor.host" as a constant in ServerProperties as part of code refactoring.
|
2/27/2017 3:09:29 PM
app metrics. (#913)
* constructing new app metrics structure to collect and send app metrics.
This commits create two singletone metrics classes, CommonMetrics and WebMetrics, which are in charge of dealing with collecting and reporting metrics, like user log fetch latency, the number of get rest call in web side. Also added corresponding tests to verify. This commit kicks off the following metrics:
* the rate of Rest Get Call in Webserver
* the rate of Rest Post Call in Webserver
* The rate of DB connection in both web and executor
* user log fetch latency
More metrics could be added easily after the app metrics structure is created.
|
