[
https://issues.apache.org/jira/browse/IGNITE-25087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-25087:
---------------------------------------
Description:
It is normal for a Raft node that is not leader anymore to get a request which
was sent when it was a leader. Some controllers just throw an
IllegalStateException in such case, which causes an exception to be logged.
This exception is basically useless as the client will retry its request using
the correct leader.
We should not log such exceptions at ERROR level.
> Do not log 'Not leader' as ERROR on leader miss
> -----------------------------------------------
>
> Key: IGNITE-25087
> URL: https://issues.apache.org/jira/browse/IGNITE-25087
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Assignee: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It is normal for a Raft node that is not leader anymore to get a request
> which was sent when it was a leader. Some controllers just throw an
> IllegalStateException in such case, which causes an exception to be logged.
> This exception is basically useless as the client will retry its request
> using the correct leader.
> We should not log such exceptions at ERROR level.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
