[
https://issues.apache.org/jira/browse/IGNITE-7577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16345904#comment-16345904
]
ASF GitHub Bot commented on IGNITE-7577:
----------------------------------------
GitHub user agoncharuk opened a pull request:
https://github.com/apache/ignite/pull/3455
IGNITE-7577 Fixing public API active flag on baseline changes
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7577
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3455.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3455
----
commit 41cffaafa5deef039a14e057152d45399a0b97fc
Author: Alexey Goncharuk <alexey.goncharuk@...>
Date: 2018-01-30T22:16:01Z
IGNITE-7577 Fixing public API active flag on baseline changes
----
> GridClusterStateProcessor#publicApiActiveState returns false when baseline
> change is in progress
> ------------------------------------------------------------------------------------------------
>
> Key: IGNITE-7577
> URL: https://issues.apache.org/jira/browse/IGNITE-7577
> Project: Ignite
> Issue Type: Bug
> Components: persistence
> Affects Versions: 2.4
> Reporter: Alexey Goncharuk
> Assignee: Alexey Goncharuk
> Priority: Major
> Fix For: 2.5
>
>
> Currently the method checks for the transition state, but it does not check
> if the active flag is changing. This leads to unexpected 'Cluster is not
> active' exceptions during baseline change.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
