1/16/2019 3:42:55 PM
3.67.0
caused the jobs to hang.
Commits to revert:
-Remove unused code (661351f). This is the commit that's causing the issue. It eliminated code that read from the standard output of a subprocess but did nothing with it. That caused the subprocess’ standard output to not be consumed, so when the pipe was full the process blocked trying to write to standard output.
-Log kill command failures when killing jobs (734f01b)
|
1/16/2019 12:00:37 AM
(#2088)
* AZNewDispatchingLogic - Enable JMX for ExecutionController
* update javadoc.
* update copyright year
* address comment
|
1/11/2019 3:57:21 PM
(#1994)
* Don't delete (clean) project versions with running executions
When a new version of a project is uploaded, the old versions are cleaned up (zip files are deleted from the DB).
This way the project versions with running executions are skipped in the old versions cleanup.
Even those versions will be eventually cleaned up once those executions have finished, because the basic filter is `version < ?`
* Use ExecutorLoader instead of RunningExecutions
* Use unfinishedExecutions to also cover queued flows
As an optimization, fetch the unfinished executions without full flow data, as that's not needed
* Include submit_user in unfinished flow metadata
* Renamed method: fetchUnfinishedExecutions
* Renamed method: getExecutableFlowMetadataHelper
* More naming fixes: ~fetchUnfinishedFlowsMetadata
* Improve javadoc of cleanOlderProjectVersion
* Fix test name -> testFetchUnfinishedFlowsMetadata
* Implement MockExecutorLoader#fetchUnfinishedFlowsMetadata
|
1/7/2019 5:44:13 PM
3.66.0
to make it more exposable to azkaban users as we have heard from internal users that they didn't know some of the useful azkaban features(like auto-retry on job failure) until they did fair amount of researching.
|
1/7/2019 5:07:05 PM
Log kill command failures when killing jobs.
* Remove unused code
|
1/4/2019 8:12:11 PM
(#2085)
|
|
|
1/2/2019 11:11:54 PM
when flow finishes (#2080)
|
|
|
|
|
