[jira] [Assigned] (RATIS-2068) Logs with entire StateMachine data is painful to read

["Duong (Jira)" <ji...@apache.org>]

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

Duong reassigned RATIS-2068:
----------------------------

    Assignee: Duong

> Logs with entire StateMachine data is painful to read
> -----------------------------------------------------
>
>                 Key: RATIS-2068
>                 URL: https://issues.apache.org/jira/browse/RATIS-2068
>             Project: Ratis
>          Issue Type: Improvement
>            Reporter: Duong
>            Assignee: Duong
>            Priority: Major
>
> Today, Ratis sometimes logs entire LogEntry messages with StateMachine data, for example:
> {code:java}
> @Override
> public CompletableFuture<AppendEntriesReplyProto> appendEntriesAsync(
>     ReferenceCountedObject<AppendEntriesRequestProto> requestRef) throws IOException {
>   .....
>   } catch(Exception t) {
>     LOG.error("{}: Failed appendEntries* {}", getMemberId(), toAppendEntriesRequestString(r), t);
>    ....
>    } 
> } {code}
> This makes the logs painful to read for large StateMachine data scenarios. Specifically, in Ozone, StateMachine data is usually 4mb, and we see 4M-letters log lines which are very hard to navigate around. 
> We should either filter StateMachine data when logging or restrict the log message to a certain limit. 



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