[
https://issues.apache.org/jira/browse/HADOOP-18091?focusedWorklogId=713399&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-713399
]
ASF GitHub Bot logged work on HADOOP-18091:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 23/Jan/22 19:18
Start Date: 23/Jan/22 19:18
Worklog Time Spent: 10m
Work Description: steveloughran commented on pull request #3916:
URL: https://github.com/apache/hadoop/pull/3916#issuecomment-1019549756
Turning off logging by default is the fastest way to address this issue,
while I do something better involving a thread id map with weak references to
spans. and with a test to verify memory problems are avoided.
running the full test suite with the default settings (i.e. auditing is
disabled)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 713399)
Time Spent: 20m (was: 10m)
> S3A auditing leaks memory through ThreadLocal references
> --------------------------------------------------------
>
> Key: HADOOP-18091
> URL: https://issues.apache.org/jira/browse/HADOOP-18091
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.3.2
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Blocker
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {{ActiveAuditManagerS3A}} uses thread locals to map to active audit spans,
> which (because they are wrapped) include back reference to the audit manager
> instance and the config it was created with.
> these *do not* get cleaned up when the FS instance is closed.
> if you have a long lived process creating and destroying many FS instances,
> then memory gets used up. l
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
