You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Yaroslav Molochkov (Jira)" <ji...@apache.org> on 2020/11/03 15:09:00 UTC

[jira] [Updated] (IGNITE-13534) Using a Deprecated method and uninformative message in console

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

Yaroslav Molochkov updated IGNITE-13534:
----------------------------------------
    Fix Version/s: 2.9.1

> Using a Deprecated method and uninformative message in console
> --------------------------------------------------------------
>
>                 Key: IGNITE-13534
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13534
>             Project: Ignite
>          Issue Type: Improvement
>          Components: general
>            Reporter: Ilya Kazakov
>            Assignee: Ilya Kazakov
>            Priority: Minor
>              Labels: 2.9.1-rc
>             Fix For: 2.10, 2.9.1
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> When cluster started in INACTIVE status in console writes uninformative message:
> {code:java}
> >>> Ignite cluster is not active (limited functionality available). Use control.(sh|bat) script or IgniteCluster interface to activate.{code}
> This message contains two words "active" and not contain word "state". 
> From this message, users try use deprecated IgniteCluster.active(boolean active), but need to use IgniteCluster.state(ClusterState newState)
> Also there are 3 calls of this deprecated method IgniteCluster.active in IgniteKernal.class



--
This message was sent by Atlassian Jira
(v8.3.4#803005)