You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Kirill Tkalenko (Jira)" <ji...@apache.org> on 2024/07/31 15:11:00 UTC

[jira] [Updated] (IGNITE-22869) Fix some NetworkMessage logging

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

Kirill Tkalenko updated IGNITE-22869:
-------------------------------------
    Fix Version/s: 3.0.0-beta2

> Fix some NetworkMessage logging
> -------------------------------
>
>                 Key: IGNITE-22869
>                 URL: https://issues.apache.org/jira/browse/IGNITE-22869
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Kirill Tkalenko
>            Assignee: Kirill Tkalenko
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>          Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> Judging from the crash [logs|https://ci.ignite.apache.org/viewLog.html?buildId=8358647&tab=buildResultsDiv&buildTypeId=ApacheIgnite3xGradle_Test_IntegrationTests_ModuleTable], long stack traces were found due to logging of *NetworkMessage*, it is proposed to fix this.
> Methods that were found:
> * org.apache.ignite.internal.network.TrackableNetworkMessageHandler#maybeLogLongProcessing
> * org.apache.ignite.internal.raft.RaftGroupServiceImpl#handleThrowable
> * org.apache.ignite.internal.network.DefaultMessagingService#logMessageSkipDueToSenderLeft
> Perhaps more corrections will be found along the way.



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