[
https://issues.apache.org/jira/browse/NIFI-9639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17487404#comment-17487404
]
ASF subversion and git services commented on NIFI-9639:
-------------------------------------------------------
Commit 94668dee6e0da404a8ba7ba03a5d13ce315ce196 in nifi's branch
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=94668de ]
NIFI-9639: Determine how long it takes to find cluster coordinator and perform
DNS lookup when sending heartbeats and include in the logs
This closes #5748
Signed-off-by: David Handermann <[email protected]>
> 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
> Time Spent: 10m
> 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)
