[
https://issues.apache.org/jira/browse/RATIS-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duong updated RATIS-2185:
-------------------------
Summary: Ratis logs debugability (was: Improve Ratis logs)
> Ratis logs debugability
> -----------------------
>
> Key: RATIS-2185
> URL: https://issues.apache.org/jira/browse/RATIS-2185
> Project: Ratis
> Issue Type: Improvement
> 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)
