[
https://issues.apache.org/jira/browse/HADOOP-19280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17914877#comment-17914877
]
ASF GitHub Bot commented on HADOOP-19280:
-----------------------------------------
bhattmanish98 commented on PR #7061:
URL: https://github.com/apache/hadoop/pull/7061#issuecomment-2603860423
> Manish, thank you!
>
> Please can you do a backport PR for branch-3.4; this is simply for testing
rather than any more code reviews.
@steveloughran Applogies for the delay. I have raised a PR
(https://github.com/apache/hadoop/pull/7307) to backport these changes to
branch-3.4.
Thanks
> ABFS: Initialize ABFS client timer only when metric collection is enabled
> -------------------------------------------------------------------------
>
> Key: HADOOP-19280
> URL: https://issues.apache.org/jira/browse/HADOOP-19280
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/azure
> Affects Versions: 3.4.0, 3.4.1
> Reporter: Manish Bhatt
> Assignee: Manish Bhatt
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.5.0
>
>
> In the current flow, we are initializing the timer of the
> {{abfs-timer-client}} outside the metric collection enable check. As a
> result, for each file system, when the {{AbfsClient}} object is initialized,
> it spawns a thread to evaluate the time of the ABFS client. Since we are
> purging/closing the timer inside the metric collection check, these threads
> are not being closed, causing them to persist in a long-lived state. To fix
> this, we are moving the timer initialization inside the condition
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
