You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ratis.apache.org by "Tsz-wo Sze (Jira)" <ji...@apache.org> on 2024/05/13 15:22:00 UTC

[jira] [Resolved] (RATIS-2083) Timer thread leak when log level is DEBUG

     [ https://issues.apache.org/jira/browse/RATIS-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tsz-wo Sze resolved RATIS-2083.
-------------------------------
    Fix Version/s: 3.1.0
       Resolution: Fixed

The pull request is now merged.  Thanks, [~Sammi]!

> Timer thread leak when log level is DEBUG
> -----------------------------------------
>
>                 Key: RATIS-2083
>                 URL: https://issues.apache.org/jira/browse/RATIS-2083
>             Project: Ratis
>          Issue Type: Bug
>          Components: util
>            Reporter: Sammi Chen
>            Assignee: Sammi Chen
>            Priority: Major
>             Fix For: 3.1.0
>
>         Attachments: jstack_output_20240506_142709.txt
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> During a DN issue investigation, it's found that there are thousands of Timer threads in the jstack output. A further investigation shows that Ratis creates new Timer() in every SlidingWindow#RequestMap object when log level is debug.  See the attached jstack file. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)