ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-6299) Cluster state (active/inactive) should be checked on individual operations rather than on facades
Date Thu, 07 Sep 2017 13:56:02 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-6299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vladimir Ozerov updated IGNITE-6299:
------------------------------------
    Labels: usability  (was: )

> Cluster state (active/inactive) should be checked on individual operations rather than
on facades
> -------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-6299
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6299
>             Project: Ignite
>          Issue Type: Task
>          Components: general
>    Affects Versions: 2.1
>            Reporter: Vladimir Ozerov
>              Labels: usability
>             Fix For: 2.3
>
>
> When persistence is enabled cluster can be in either active or inactive state. Currently
we check cluster state only when user trying to get certain facade from {{Ignite}} interface,
but never check it on individual operations. This is wrong from usability perspective as facades
are typically long-lived objects. 
> Let's make sure that cluster state check is performed on individual operations instead.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message