ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Kovalenko (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-9111) Do not wait for deactivation in GridClusterStateProcessor#publicApiActiveState
Date Fri, 27 Jul 2018 16:30:00 GMT
Pavel Kovalenko created IGNITE-9111:
---------------------------------------

             Summary: Do not wait for deactivation in GridClusterStateProcessor#publicApiActiveState
                 Key: IGNITE-9111
                 URL: https://issues.apache.org/jira/browse/IGNITE-9111
             Project: Ignite
          Issue Type: Improvement
          Components: cache
    Affects Versions: 2.5, 2.4
            Reporter: Pavel Kovalenko
            Assignee: Pavel Kovalenko
             Fix For: 2.7


Currently, we wait for activation/deactivation future when check state of the cluster. But
when deactivation is in progress it doesn't make sense to wait for it, because after the successful
wait we will throw an exception that cluster is not active. Synchronous waiting for deactivation
future may lead to deadlocks if operation obtains some locks before checking cluster state.

As the solution, we should check and wait only for activation futures. In case of in-progress
deactivation, we should fail fast and return "false" from publicApiActiveState method.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message