9/18/2017 10:41:53 AM
#1471
|
9/17/2017 12:21:30 AM
metrics in azkaban-db module. The most important metrics are DB connection monitorings. Here's the steps to complete the task:
Create DBMetrics class;
make AzkabanDataSource Guiceable, in order to Inject DBMetrics. Adding Binding method in azkabanCommonModule to guice it;
Moving Common MetricsTestUtility method to Core module, so that db module can call it. Also, add test dependency gradle code.
After that, add 3 metrics to MysqlDataSource.
|
9/16/2017 9:43:45 PM
type instead of the Java jobtype
The old JobRunner test runs a java job that launches an additional JVM / java process. That should be the responsibility of JavaProcessJobTest, and I think it already does that.
If this test case serves any purpose, I think it should be converted to use the InteractiveTestJob which is simple and quick and lives within the test process itself.
|
9/16/2017 5:19:54 PM
(#1438)
* Faster dispatch and test for an interrupted execution
- Test for an interrupted execution ("Flow does not exist")
- Found out that wait/notify was missing for dispatching new executions, so fixed that
* Use Awaitility, In case of failure print message like: expected a finished status but was <READY> within 10 seconds.
* Upgrade mockito -> 2.10.0
|
9/16/2017 11:38:06 AM
failures. It's quick, too.
* Fix bug where pipelined execution gets stuck
If you had executed a flow with some subflows disabled and then started another execution in pipeline mode, the next execution remained blocked forever by the jobs inside sub-flows, because they remained in READY state instead of being set to SKIPPED.
This was a pretty nasty bug because for example next morning's scheduled run can get stuck after you've launched an execution with some jobs disabled on the previous day.
I think it would make sense to clean this up also on the flow saving side: when subflow status is changed from DISABLED to SKIPPED, all jobs in the subflows would also be marked as SKIPPED.
* Fix bug in FlowWatcher.peekStatus
* Test pipeline block fix with a sub-flow
This test proves (or proved) how it happens. Without the fix this new test testBasicPipelineLevel1RunDisabledJobs gets stuck.
|
9/16/2017 1:07:03 AM
FlowRunnerPipelineTest
* Fast FlowRunnerPipelineTest
Removed all sleep.
* Fix NPE in printStatuses
* Use TemporaryFolder rule for workingDir
* Use ExecutionsTestUtil to get flow files
|
9/15/2017 11:48:28 PM
instead of log4j.
- Add or update the copyright notice for most files.
- Add a link to the dev tips wiki.
- Clarify the standard form of slf4j logger
- Mention the usage of the images repo.
|
9/15/2017 2:22:20 PM
2
* commit 8
* commit 9
* fix format
This PR is a follow-up of #1463 . Moving Props and Metrics Registry to az-core module.
|
9/15/2017 2:13:54 PM
brought a feature that AZ admins can publish messages in banner bar on the top of AZ UI. There exists an issue reported by the user:
I cannot click on the "Job List", "Flow Log", and "Stats" tabs until the orange message banner disappears after about 30 seconds.
The cause is that container-fill (css class) uses absolute position, when the top div elements moves down, it will override the div beneath. I figured out there are a number of places using container-fill. So I'd like not change the original place. The proposed fix is that we just let flow view page's div to be static, such that it will move downward along with top div.
|
|
|
