GitHub user markap14 opened a pull request:
https://github.com/apache/nifi/pull/294
NIFI-1563: Federate requests and merge responses from nodes instead oâ¦
â¦f storing bulletins and stats at NCM
- Updating UI to support restructured status history DTO.
Return 'Insufficient History' message if aggregate stats don't have enough
data points, even if all nodes do (which can be the case if the node performing
the aggregation has a different value for the
'nifi.components.status.snapshot.frequency' property than the other nodes)
Bug fixes; code cleanup; replicate requests to bulletin board endpoint
Refactored the <Component>StatusDTO objects into <Component>StatusDTO,
<Component>StatusSnapshotDTO, Node<Component>StatusSnapshotDTO objects
- Introducing endpoints for accessing individual component status.
- Wiring up new endpoints and updated core.
- Code clean up.
- Starting to handling status merging of individual components.
- Nodewise breakdown has been added to Processors but the remaining
components still need to be updated.
Refactor so that System Diagnostics requests are replicated to nodes
instead of the information being pulled from Heartbeats
Replicate request for counters instead of pulling them from heartbeats
Removed the getCounters / setCounters method from HeartbeatPayload
- Implementing component specific endpoints.
- Removing unused endpoints.
- Supporting nodewise breakdown for system diagnostics and counters.
- Updating DTOs to use more consistent naming.
- Code clean up.
- Addressing contrib issues.
Removed ProcessGroupStatus from HeartbeatPayload
- Removing nodewise from the system diagnostics endpoint. Had included it
for testing that option but did not intend for it to be committed.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/markap14/nifi NIFI-1563
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/294.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 #294
----
commit 1bbe0aa7f7c80d13a67178261b88551389a92f17
Author: Mark Payne <[email protected]>
Date: 2016-03-03T18:29:34Z
NIFI-1563: Federate requests and merge responses from nodes instead of
storing bulletins and stats at NCM
- Updating UI to support restructured status history DTO.
Return 'Insufficient History' message if aggregate stats don't have enough
data points, even if all nodes do (which can be the case if the node performing
the aggregation has a different value for the
'nifi.components.status.snapshot.frequency' property than the other nodes)
Bug fixes; code cleanup; replicate requests to bulletin board endpoint
Refactored the <Component>StatusDTO objects into <Component>StatusDTO,
<Component>StatusSnapshotDTO, Node<Component>StatusSnapshotDTO objects
- Introducing endpoints for accessing individual component status.
- Wiring up new endpoints and updated core.
- Code clean up.
- Starting to handling status merging of individual components.
- Nodewise breakdown has been added to Processors but the remaining
components still need to be updated.
Refactor so that System Diagnostics requests are replicated to nodes
instead of the information being pulled from Heartbeats
Replicate request for counters instead of pulling them from heartbeats
Removed the getCounters / setCounters method from HeartbeatPayload
- Implementing component specific endpoints.
- Removing unused endpoints.
- Supporting nodewise breakdown for system diagnostics and counters.
- Updating DTOs to use more consistent naming.
- Code clean up.
- Addressing contrib issues.
Removed ProcessGroupStatus from HeartbeatPayload
- Removing nodewise from the system diagnostics endpoint. Had included it
for testing that option but did not intend for it to be committed.
----
---
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.
---
