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 2023/11/20 09:12:00 UTC

[jira] [Updated] (RATIS-1917) Print Epoll.unavailabilityCause() only once

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

Tsz-wo Sze updated RATIS-1917:
------------------------------
    Fix Version/s: 3.0.0

> Print Epoll.unavailabilityCause() only once
> -------------------------------------------
>
>                 Key: RATIS-1917
>                 URL: https://issues.apache.org/jira/browse/RATIS-1917
>             Project: Ratis
>          Issue Type: Improvement
>          Components: Netty
>            Reporter: Tsz-wo Sze
>            Assignee: Tsz-wo Sze
>            Priority: Minor
>             Fix For: 3.0.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Currently, the same Epoll.unavailabilityCause() stack trace will be printed for each epoll EventLoopGroup initialization.  We should only print stack trace in the first time and then only an error message for the following calls.



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