Great observations! Did you open a ticket? Are you interested in contributing a patch?
> On 8 Oct 2020, at 05:41, Ilya Kazakov <kazakov.i...@gmail.com> wrote: > > Hello! > > As a new user of Ignite I faced this problem. When cluster started in > INACTIVE state in logs writes uninformative message: > >>>> Ignite cluster is not active (limited functionality available). Use > control.(sh|bat) script or IgniteCluster interface to activate. > > This message contains two words "active" and does not contain the word > "state". > From this message, users try to use deprecated IgniteCluster.active(boolean > active), but need to use IgniteCluster.state(ClusterState newState) > > I propose to change this message. There are two options: >>>> Ignite cluster is in INACTIVE state (limited functionality available). > Use control.(ch|bat) script or IgniteCluster interface to change the state. > or >>>> Ignite cluster is in INACTIVE state (limited functionality available). > Use control.(ch|bat) script or IgniteCluster.state() to change the state. > > Also in the class IgniteKernal there are 3 usages of deprecated methods > active() and active(boolean b). > I propose to change > - each using .active() to .state() != ClusterState.INACTIVE > - each using .active(boolean b) to .state(b ? ClusterState.ACTIVE : > ClusterState.INACTIVE) > > --------------------- > Ilya Kazakov
