8/22/2017 6:07:05 PM
3.32.2
plugin adds an errorprone configuration that automatically uses the latest release of error-prone. You can override it to use a specific version "
see https://github.com/tbroyer/gradle-errorprone-plugin
It appears that by latest version it will use the last locally cached
version. This caused inconsistency in builds.
## Fix:
Specify a fixed version
Will update to the latest version after the internal Artifactory
is updated with the latest version.
## Test:
Deleted the gradle cache and run the build again and verified in the
console output that the specified version was downloaded.
|
8/24/2017 7:56:40 PM
(#1346)
Added a config azkaban.storage.artifact.max.retention(default: 0)
Based on the storage parameter the files are removed and the project_versions table entries are removed.
``` /* * The max number of artifacts retained per project. * Accepted Values: * - 0 : Save all artifacts. No clean up is done on storage. * - 1, 2, 3, ... (any +ve integer 'n') : Maintain 'n' latest versions in storage * * Note: Having an unacceptable value results in an exception and the service would REFUSE * to start. * * Example: * a) azkaban.storage.artifact.max.retention=all * implies save all artifacts * b) azkaban.storage.artifact.max.retention=3 * implies save latest 3 versions saved in storage. **/ public static final String AZKABAN_STORAGE_ARTIFACT_MAX_RETENTION = "azkaban.storage.artifact.max.retention";
```
|
8/15/2017 6:39:31 PM
local storage uses hash to create a filename. With the current code it generates weird characters in the file name. Updating the logic to the one similar with `HdfsStorage`. This fixes the filename issue.
Example old filename: 1/1-���ΰ�LJ�.����*�.zip
Example new filename: 1/1-c5e616ceb09bc787e52eb99bab8d2a8c.zip
|
8/15/2017 7:07:34 PM
API implementation was missing from LocalStorage. Added it. Updated test.
|
8/11/2017 11:22:08 AM
delete API based on a key. The key is the relative path of the project file and is stored as `resourceId` in the DB.
|
|
|
8/2/2017 7:54:11 PM
login warning (#1303)
This commit reverts the XMLUserManager code since it is found that we don't need to customize XML error login message, since only headless users access from XMLUserManager. Standard users go through LDAPUserManager, which we already added this feature.
The original PR is at: #1277
|
8/2/2017 7:14:11 PM
class (#1294)" (#1304)
This reverts commit 9d079ec.
This change removed an API (getSessionData) relied upon by the hdfs viewer.
|
8/1/2017 3:14:21 PM
3.32.0
commit d1b836a.
Conflicts:
azkaban-common/src/main/java/azkaban/executor/Status.java
azkaban-exec-server/src/main/java/azkaban/execapp/JobRunner.java
From @jamiesjc: When we kill the flow immediately after it starts in our integration test, it couldn't be killed due to some race condition. Users will see on the execution page that the job is in KILLING status but it actually never gets killed. And users cannot click kill button again during the KILLING period.
At the time when we kill, the process might not have started yet or the jobRunner has not yet been added to the activeJobRunners.
You can check more details in the PR description: #1289. We are still working on the fix.
The intention is to reintroduce this commit once the underlying bug is fixed.
|
7/31/2017 6:38:27 PM
logs every hour
We observed the long deletion transaction in our production Azkaban cluster. In mysql, if delete transaction is large (The data going to be deleted is too big), it occupies too much undo space (buffer), which affect other transactions and other databases in this host. So we change every day one time's deletion to every hour.
|
