You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Steshin (Jira)" <ji...@apache.org> on 2023/02/06 20:02:00 UTC
[jira] [Updated] (IGNITE-18726) Repeated state-changed message on same cluster state.
[ https://issues.apache.org/jira/browse/IGNITE-18726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Steshin updated IGNITE-18726:
--------------------------------------
Summary: Repeated state-changed message on same cluster state. (was: State-changed message on not changed cluster state.)
> Repeated state-changed message on same cluster state.
> -----------------------------------------------------
>
> Key: IGNITE-18726
> URL: https://issues.apache.org/jira/browse/IGNITE-18726
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladimir Steshin
> Assignee: Vladimir Steshin
> Priority: Minor
> Labels: ise
>
> When user requests cluster change state by Ignite client on same state, 'Cluster state shanged to...' arises. It is better to say that cluste is already on this state.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)