5/14/2017 6:14:53 PM
Updated build instructions - Remove '3' from title - cosmetic: minor rewording
|
5/11/2017 4:04:28 PM
the project name to the body of Azkaban emails when flows succeed or fail. Will help users better identify succeeding/failing flows. Done at the request of a user.
|
5/10/2017 10:25:24 PM
(#1076)
* Fix race condition caused by UpdaterThread in ExecutorManager
* Fix logger message for PR #1076
|
5/10/2017 2:56:51 PM
exists a bug in property override messages. when inserting a wholy new props, AZ triggers an NPE through guava library. We enforce Props to always have concrete instance to solve this problem.
|
|
|
5/9/2017 7:32:08 PM
for Azkaban.
Setting up requires the following configuration.
```
# Set the storage type to HDFS
azkaban.storage.type=HDFS
# Tell Azkaban where to find Hadoop Configuration
hadoop.conf.dir.path=/path/to/hadoop/etc/hadoop
# All projects are stored inside the root directory in the format
# <project_id>/<project_id>_<hex(md5-hash-of-file)>.zip
azkaban.storage.hdfs.root.uri=hdfs://hadoop-name-node:9000/tmp/azkaban/root
# For Kerberized Hadoop Cluster
azkaban.keytab.path=/path/to/keytab.file
azkaban.kerberos.principal=user/host@REALM
```
Local Storage bug fix.
Duplicate file in storage just logs the info and not raise an exception.
|
5/9/2017 1:15:46 AM
to [Google style](https://github.com/google/styleguide). No code has been reformatted yet.
Instructions for setup are available here:
https://github.com/HPI-Information-Systems/Metanome/wiki/Installing-the-google-styleguide-settings-in-intellij-and-eclipse
|
|
|
5/8/2017 8:35:23 PM
string for H2 DB needs to be an absolute path.
Has to make the change in two different places since the data source
is currently configured in two places.
Testing:
Tested manually the solo server with the following config:
```
# h2 db
database.type=h2
h2.path=data/azkaban
h2.create.tables=true
```
|
5/8/2017 6:18:21 PM
3.23.0
finis… (#1062)
* Fix bugs in resubmitting flow and fetching flow logs after flow finishes.
After removing runningFlows cache from web server, running flow info will be fetched from DB directly by ExecutorManager. This includes the flow updateTime which is updated by FlowRunnerManager when the flow finishes. Currently the UpdaterThread in ExecutorManager will send update request to executor to get updated flow info. UpdateTime now is synced between web server and executor since they all update and get from DB instead of cache, the previous logic of comparing updateTime should be changed.
TODO: updaterThread in executorManager should be removed in the future to simplify the logic. handleAjaxUpdateRequest() should be deprecated as well.
|
