[
https://issues.apache.org/jira/browse/NIFI-8405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17317471#comment-17317471
]
ASF subversion and git services commented on NIFI-8405:
-------------------------------------------------------
Commit 14e6dc3dc6533fc6189a301cf720c0ee57650729 in nifi's branch
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=14e6dc3 ]
NIFI-8405: Added debug logging around how long it takes to establish
connections/query dns/read and write headers and body when replication
requests; added additional timing around Ranger audits and authorizations and
monitoring of long-running tasks because those run often and frequently show up
in the logs at the same time as the long requests
This closes #4983
Signed-off-by: David Handermann <exceptionfact...@apache.org>
> Add debug logging around request replication
> --------------------------------------------
>
> Key: NIFI-8405
> URL: https://issues.apache.org/jira/browse/NIFI-8405
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> I'll occasionally have a cluster where some requests take a lot longer on one
> node than others (a couple of seconds vs. tens of milliseconds).
> We should add logging information that indicates timing information around
> some of the critical components involved in that path.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
