[ 
https://issues.apache.org/jira/browse/IGNITE-18726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17685718#comment-17685718
 ] 

Ignite TC Bot commented on IGNITE-18726:
----------------------------------------

{panel:title=Branch: [pull/10522/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10522/head] Base: [master] : No new tests 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=7061556&buildTypeId=IgniteTests24Java8_RunAll]

> 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
>             Fix For: 2.15
>
>
> 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)

Reply via email to