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/11/04 17:02:00 UTC

[jira] [Updated] (RATIS-2185) Improve gRPC log messages debugability

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

Tsz-wo Sze updated RATIS-2185:
------------------------------
    Component/s: gRPC
        Summary: Improve gRPC log messages debugability  (was: Ratis logs debugability)

Since the problem mentioned are in gRPC, updating the Summary.

> Improve gRPC log messages debugability
> --------------------------------------
>
>                 Key: RATIS-2185
>                 URL: https://issues.apache.org/jira/browse/RATIS-2185
>             Project: Ratis
>          Issue Type: Improvement
>          Components: gRPC
>            Reporter: Duong
>            Priority: Major
>
> Created this as a umbrella ticket for all changes related to improve the debugability of Ratis logs.
> Today, there're a couple of issues with ratis logs making debug issues in ratis a hard job. For example:
>  * Lack of details: when an RPC call, e.g. appendEntries calls, fail, there is very little information to identify the problem, exception some vague message like "Unavailable" or "Client cancelled".  We've seen examples where "Client cancelled" is displayed for technical problem in GRPC layer, e.g. when appendEntries buffers are bigger than the max GRPC acceptable message size.
>  * Repetitive: TBF



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