You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by GitBox <gi...@apache.org> on 2020/03/01 02:00:37 UTC
[GitHub] [hadoop-ozone] runzhiwang edited a comment on issue #611:
[WIP]HDDS-3041. Fix the memory leak of s3g by releasing the connection
resource
runzhiwang edited a comment on issue #611: [WIP]HDDS-3041. Fix the memory leak of s3g by releasing the connection resource
URL: https://github.com/apache/hadoop-ozone/pull/611#issuecomment-592508704
@elek Hi, thank you for your reply. Because you would check the code, so I want to share you some information I have found. If with this patch, s3g will occupy all the cpu, as the image shows the cpu cost of s3g increases to 2381% in the machine with 24 cores, it's horrible. When use jstack, I find a lot of threads are in the state:waiting to lock. I will continue to find the root cause.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org