Hello!

I think the restart of your nodes is what fixed it for you.

Regards,
-- 
Ilya Kasnacheev


пн, 2 дек. 2019 г. в 13:25, ?青春狂-^ <yukai...@qq.com>:

> Hi
>    I used bin/control.sh --host 172.17.122.126 --activate
>
> But it still did not work properly, it print “ [WARN ] Can not perform
> the operation because the cluster is inactive.”
>
> I changed the config file by added ports,  I found this config can use
> "top " or other commands ,it seem work properly , the config is:
> <property name="addresses">
>                             <list>
>                                 <value>172.17.122.126:47500..47509</value>
>                                 <value>172.17.122.127:47500..47509</value>
>                                 <value>172.17.122.128:47500..47509</value>
>                             </list>
>                         </property>
>
> before this ,config is :
> <property name="addresses">
>                             <list>
>                                 <value>172.17.122.126</value>
>                                 <value>172.17.122.127</value>
>                                 <value>172.17.122.128</value>
>                             </list>
>                         </property>
>
> I dont know why?
>
> ------------------ 原始邮件 ------------------
> *发件人:* "Ilya Kasnacheev"<ilya.kasnach...@gmail.com>;
> *发送时间:* 2019年11月29日(星期五) 下午5:27
> *收件人:* "user"<user@ignite.apache.org>;
> *主题:* Re: can't use "cache -a "command , warn info is " the cluster is
> inactive"
>
> Hello!
>
> You have to activate your cluster, by doing something like
>
> bin/control.sh --host 172.17.122.126 --activate
>
> This is a requirement on the first start of persistent cluster, after all
> nodes has joined.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пт, 29 нояб. 2019 г. в 11:34, ?青春狂-^ <yukai...@qq.com>:
>
>> because of the program'Exception, I wanted to see the cache infos.
>> so I use the ./ignitevisorcmd.sh  command.
>> then I use "open -d"
>> and  "cache -a"
>>
>> but it print warn info :
>> [WARN ] Can not perform the operation because the cluster is inactive.
>>
>>
>> I have 3 nodes of ignite ,and process is alive.
>>
>> the config xml is :
>>
>>   <property name="discoverySpi">
>>             <bean
>> class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
>>                 <property name="ipFinder">
>>                     <bean
>> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>>                         <property name="addresses">
>>                             <list>
>>                                 <value>172.17.122.126</value>
>>                                 <value>172.17.122.127</value>
>>                                 <value>172.17.122.128</value>
>>                             </list>
>>                         </property>
>>                     </bean>
>>                 </property>
>>             </bean>
>>         </property>
>>     </bean>
>>
>>

Reply via email to