[
https://issues.apache.org/jira/browse/NIFI-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14741209#comment-14741209
]
Matt Gilman commented on NIFI-948:
----------------------------------
[~markap14] A couple of notes...
- The default configuration in bootstrap.conf was a little confusing at first.
Should we consider treating all notification service properties the same? All
commented out with a default value? Or all not commented out with no default
value? The fact that there was a mix made me think that it was significant for
some reason. I realize showing a default value is beneficial for the user so
maybe we go that route? Thoughts?
- For some reason only the STARTED notification is actually notifying (via
email). I can populate each event with the same notification service but I only
receive notifications for STARTED. Through some debugging it appears all the
events are triggering but only STARTED is actually being emailed.
- In doing the additional debugging trying to figure out the previous issue, it
appears that a STOPPED and DIED event is triggered when I issued a stop command
to the bootstrap. Should a DIED event be triggered here?
- When using the run command with the bootstrap, no STOPPED or DIED events
where triggered when I exited the application using Ctrl-C. Shouldn't a STOPPED
event have been triggered here?
> NiFi doesn't provide any mechanism for alerting users that the wrapper
> restarted it
> -----------------------------------------------------------------------------------
>
> Key: NIFI-948
> URL: https://issues.apache.org/jira/browse/NIFI-948
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Fix For: 0.3.0
>
> Attachments:
> 0001-NIFI-948-Provide-capability-to-register-notification.patch
>
>
> Testing various edge conditions with out of disk space, out of memory errors,
> etc., I'm often causing nifi to die or to fail to start (intentionally). But
> the wrapper never notifies anyone that anything has happened. It should
> provide a mechanism for alerting interested parties when it restarts nifi.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
