GitHub user ijokarumawak opened a pull request:
https://github.com/apache/nifi/pull/575
NIFI-619: Make MonitorActivity more cluster friendly
- Added 'Monitoring Scope' property
- Persist the latest activity as Cluster state
- Examine cluster state on each node if necessary
<img width="762" alt="monitoractivity-config"
src="https://cloud.githubusercontent.com/assets/1107620/16346160/d7526104-3a80-11e6-85eb-f9a6fd8af206.png">
## Test
- Setup data flow as shown in the screenshot, using a 3 node cluster
- GenerateFlowFile is scheduled on primary.
- Monitoring Scope = Node
- [ok] Even if GenerateFlowFile is running, non-primary nodes will
report inactive messages.
- [ok] If GenerateFlowFile stops, all nodes report inactive messages.
- [ok] If GenerateFlowFile resumes, primary node reports
activity.restored, but other nodes don't
- Monitoring Scope = Cluster
- [ok] While GenerateFlowFile is running, none of nodes reports
inactive messages.
- [ok] If GenerateFlowFile stops, all nodes report inactive messages.
- [ok] If GenerateFlowFile resumes, all node reports
activity.restored, if copy attribute is true, then non-primary nodes copy
attributes from state.
- Confirmed it works on Standalone NiFi instance, too
<img width="955" alt="monitoractivity-test"
src="https://cloud.githubusercontent.com/assets/1107620/16346162/d920d344-3a80-11e6-886b-2acd54315968.png">
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ijokarumawak/nifi nifi-619
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/575.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #575
----
commit 3726e34eb6cb5c568ee14fa0262faf1968435dd8
Author: Koji Kawamura <[email protected]>
Date: 2016-06-24T17:52:07Z
NIFI-619: Make MonitorActivity more cluster friendly
- Added 'Monitoring Scope' property
- Persist the latest activity as Cluster state
- Examine cluster state on each node if necessary
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---