[
https://issues.apache.org/jira/browse/NIFI-4809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16408618#comment-16408618
]
ASF GitHub Bot commented on NIFI-4809:
--------------------------------------
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/2575
I saw the "unable to find schema" issue in the last PR too, it seems to be
related to the onPropertyModified() method of AvroSchemaRegistry, that's where
the actual schemas get populated, but while debugging I saw that the name was
in the schema map but there was no actual schema stored. Not sure if this is a
lifecycle order-of-operations thing or not, but when I deleted the schema from
the registry, saved it, then added it back, it worked. Just some extra info
while you're pathfinding :)
> Implement a SiteToSiteMetricsReportingTask
> ------------------------------------------
>
> Key: NIFI-4809
> URL: https://issues.apache.org/jira/browse/NIFI-4809
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Major
>
> At the moment there is an AmbariReportingTask to send the NiFi-related
> metrics of the host to the Ambari Metrics Service. In a multi-cluster
> configuration, or when working with MiNiFi (Java) agents, it might not be
> possible for all the NiFi instances (NiFi and/or MiNiFi) to access the AMS
> REST API.
> To solve this problem, a solution would be to implement a
> SiteToSiteMetricsReportingTask to send the data via S2S to the "main" NiFi
> instance/cluster that will be able to publish the metrics into AMS (using
> InvokeHTTP). This way, it is possible to have the metrics of all the
> instances exposed in one AMS instance.
> I propose to send the data formatted as we are doing right now in the Ambari
> reporting task. If needed, it can be easily converted into another schema
> using the record processors once received via S2S.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
