[ https://issues.apache.org/jira/browse/IGNITE-22599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vyacheslav Koptilin reassigned IGNITE-22599: -------------------------------------------- Assignee: Vladislav Pyatkov > Exception inside RAFT listener does not invoke falure handler > ------------------------------------------------------------- > > Key: IGNITE-22599 > URL: https://issues.apache.org/jira/browse/IGNITE-22599 > Project: Ignite > Issue Type: Bug > Reporter: Vladislav Pyatkov > Assignee: Vladislav Pyatkov > Priority: Major > Labels: ignite-3 > Attachments: > poc-tester-SERVER-192.168.1.41-id-0-2024-06-27-09-14-17-client.log.2 > > > h3. Motivation > An exception that is thrown during handling RAFT command cannot be recovered, > because a RAFT storage is already corrupted. This is a reason to call Falure > handler: > {code:java} > failureProcessor.process(new FailureContext(CRITICAL_ERROR, err)); > {code} > Currently, I do not see any FH invokation in the log, but many exception has > been thrown. > h3. Definition of done > FH is invoked in the case where RAFT listener fails. > h3. Implementation Notes > * Failure handler should be invoked in case of critical exceptions while > onWrite processing onRead processing, snapshotting and snapshot installation. > * While testing, it's required to test all CMG MG and Partition listeners. > * In order to ease testing, it worth implementing a test failure handler in > order to detect that it was triggered. -- This message was sent by Atlassian Jira (v8.20.10#820010)