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

["Tsz-wo Sze (Jira)" <ji...@apache.org>]

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

Tsz-wo Sze resolved RATIS-2185.
-------------------------------
    Fix Version/s: 3.2.0
         Assignee: Tsz-wo Sze
       Resolution: Fixed

The [pr #1186|https://github.com/apache/ratis/pull/1186] is now merged.

Thanks [~duongnguyen] and [~weichiu] for raising up this JIRA and the discussion!
{quote}These messages are provided by the StatusRuntimeException from gRPC. Ratis may be able to somehow detect such cases and then print some better messages.
{quote}
We did not fix it here. We could do it in a separated JIRA if there is a need.

> 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
>            Assignee: Tsz-wo Sze
>            Priority: Major
>             Fix For: 3.2.0
>
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> 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)