[
https://issues.apache.org/jira/browse/NIFI-9639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-9639:
-----------------------------------
Fix Version/s: 1.16.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Add additional information in heartbeat logging about how long each step takes
> ------------------------------------------------------------------------------
>
> Key: NIFI-9639
> URL: https://issues.apache.org/jira/browse/NIFI-9639
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.16.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When we send a heartbeat to the cluster coordinator, we log how long it took
> to send the heartbeat. But if we see that it takes a really long time to send
> the heartbeat, we don't have any indication of why. We should add to that log
> message information about how long it took to determine which node is the
> cluster coordinator, and how long the DNS lookup to communicate with that
> node takes.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
