7/19/2016 6:42:59 AM
mention about "executor bounce"[1]
- Fixed e-mail subject of first error message: "failed" => "encountered a failure"
- All flow notification e-mails to include flow status (as asked by @georgezhlw and @HappyRay)
- Created a unit test for DefaultMailCreator
--
[1] One of the "Reason" messages for all flow failure alerts used to be this:
> Executor no longer seems to be running this execution. Most likely due to executor bounce.
Usually the alert comes because a job itself failed. It's confusing to suggest that executor node would've been restarted, when it's not.
|
|
|
|
|
7/1/2016 2:09:09 PM
handles during Project Upload
|
4/6/2016 10:07:12 PM
during project upload.
|
6/6/2016 9:00:43 PM
getProjectId AJAX endpoint
|
|
|
|
|
6/3/2016 9:26:24 PM
changes to analyze execution with an external analyzer like Dr. Elephant
|
5/26/2016 3:20:26 AM
feature is turned off by default and can be enabled by configuring properties
in 'azkaban.properties'. When turned on a button will appear in the flow execution
details page which can query the external analyzer with the flow execution id.
Please refer to 'azkaban.properties' to know more about the configuration details.
|
