[
https://issues.apache.org/jira/browse/NIFI-9538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17547523#comment-17547523
]
ASF subversion and git services commented on NIFI-9538:
-------------------------------------------------------
Commit b5e61109f6d5d7331d7cd0c7027ad9250c347852 in nifi's branch
refs/heads/dependabot/maven/nifi-nar-bundles/nifi-standard-services/nifi-hbase_1_1_2-client-service-bundle/org.apache.hadoop-hadoop-common-3.2.3
from Matt Burgess
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=b5e61109f6 ]
NIFI-9538: Add C2 heartbeat capability to minifi-c2-service
- Added content hash code to avoid repeatedly updating with the same flow
- Gracefully handle agent classes and provide update URL to /config
- Fixed JDK 8 build issue with ConfigService
This closes #5755.
Signed-off-by: Kevin Doran <[email protected]>
> Add heartbeat capability to MiNiFi "C2 Server"
> ----------------------------------------------
>
> Key: NIFI-9538
> URL: https://issues.apache.org/jira/browse/NIFI-9538
> Project: Apache NiFi
> Issue Type: New Feature
> Components: MiNiFi
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Priority: Major
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> Before NIFI-9533 is implemented, basic heartbeat functionality could be
> implemented in the MiNiFi "C2 Server" to give it at least some C2
> capabilities. Specifically, the "heartbeat loop" (HEARTBEAT request and
> response) endpoint with an UPDATE operation would align more closely with the
> C2 protocol and still offer the same capabilities as the existing server
> (i.e. updating a flow on the agent). The operation ACKNOWLEDGE endpoint could
> be implemented as well, to represent the full C2 communications cycle
> (HEARTBEAT, operation(s), ACKNOWLEDGE) although it needs not perform any work
> (except to log its receipt).
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
