Re: ignitevisor starting the node twice

Matt, Could you share more details? I think it is possible that "invisible / daemon node" could store some state... But We need a reproducible example. On Tue, May 30, 2017 at 1:10 PM, Matt wrote: > Based on experience I would say that that "invisible node" is not > completely transparent to th

Re: ignitevisor starting the node twice

Based on experience I would say that that "invisible node" is not completely transparent to the rest of the nodes. I'm not quite sure when or how, but I've seen it changes the behavior of the other nodes sometimes. I haven't payed much attention to this (I will next time) but may it be that it kee

Re: ignitevisor starting the node twice

You need to open configuration with proper discovery. Usually that means - open same config you used to start your "real" nodes. On Tue, May 30, 2017 at 8:45 AM, I PVP wrote: > Alexey, > > Thanks for answering. > > How do I make ignitevisorcmd.sh see my “real” node(s) ? > > best, > > IPVP > >

Re: ignitevisor starting the node twice

Alexey, Thanks for answering. How do I make ignitevisorcmd.sh see my “real” node(s) ? best, IPVP On May 29, 2017 at 10:39:41 PM, Alexey Kuznetsov (akuznet...@apache.org) wrote: Hi, IPVP. Yes, ignitevisorcmd.sh starts internal node in "daemon" mode. This node

Re: ignitevisor starting the node twice

Hi, IPVP. Yes, ignitevisorcmd.sh starts internal node in "daemon" mode. This node is "invisible" for other nodes and doe not have caches data and does not participate in compute task executions. See: IgniteConfiguration#setDaemon javadocs for more info. On Sat, May 27, 2017 at 9:19 PM, I PVP w

ignitevisor starting the node twice

Does ignitevisorcmd.sh starts the node or is it a management interface? Why ignitevisorcmd.sh behaves like if Ignite was not started and does not see the cache that was created? ignite.sh starts fine. But, when I start ignitevisorcmd.sh and type the open command it asks me for the configurat