Re: ignitevisor starting the node twice

2017-06-05 Thread Alexey Kuznetsov 
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 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 keeps some state even when all other nodes are down?
>
> I'm guessing that it keeps alive classes that were loaded using peer class
> loading (with default config), and when we relaunch some real nodes the
> state of the grid is not completely pristine.
>
> Not sure if that in particular is the case, but I've seen some weird
> things when visor is running.
>
> Matt
>
> On Mon, May 29, 2017 at 11:18 PM, Alexey Kuznetsov 
> wrote:
>
>> 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
>>>
>>> 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 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  wrote:
>>>
 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 configuration file and  even informing
 the same configuration file used to start ignite   ignitevisor  says:
  "Ignite node started OK”  ,  it shows 00:00:00 uptime and the cache
 command says "(wrn) : No caches found."

 Ignite is being started with "ignite.sh config/ignite-config.xml”

 ignite-config.xml has the following content:

 -
 

 http://www.springframework.org/schema/beans";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd”>

 

   
  
 
 
 
 
  
   

 

 
 -

 Thanks
  IPVP


>>>
>>>
>>> --
>>> Alexey Kuznetsov
>>>
>>>
>>
>>
>> --
>> Alexey Kuznetsov
>>
>
>


-- 
Alexey Kuznetsov

Re: ignitevisor starting the node twice

2017-05-29 Thread Matt 
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 keeps some state even when all other nodes are down?

I'm guessing that it keeps alive classes that were loaded using peer class
loading (with default config), and when we relaunch some real nodes the
state of the grid is not completely pristine.

Not sure if that in particular is the case, but I've seen some weird things
when visor is running.

Matt

On Mon, May 29, 2017 at 11:18 PM, Alexey Kuznetsov 
wrote:

> 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
>>
>> 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 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  wrote:
>>
>>> 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 configuration file and  even informing the
>>> same configuration file used to start ignite   ignitevisor  says:  "Ignite
>>> node started OK”  ,  it shows 00:00:00 uptime and the cache command says
>>> "(wrn) : No caches found."
>>>
>>> Ignite is being started with "ignite.sh config/ignite-config.xml”
>>>
>>> ignite-config.xml has the following content:
>>>
>>> -
>>> 
>>>
>>> http://www.springframework.org/schema/beans";
>>>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>>>xsi:schemaLocation="
>>>http://www.springframework.org/schema/beans
>>>http://www.springframework.org/schema/beans/spring-beans.xsd”>
>>>
>>> 
>>>
>>>   
>>>  
>>> 
>>> 
>>> 
>>> 
>>>  
>>>   
>>>
>>> 
>>>
>>> 
>>> -
>>>
>>> Thanks
>>>  IPVP
>>>
>>>
>>
>>
>> --
>> Alexey Kuznetsov
>>
>>
>
>
> --
> Alexey Kuznetsov
>

Re: ignitevisor starting the node twice

2017-05-29 Thread Alexey Kuznetsov 
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
>
> 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 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  wrote:
>
>> 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 configuration file and  even informing the
>> same configuration file used to start ignite   ignitevisor  says:  "Ignite
>> node started OK”  ,  it shows 00:00:00 uptime and the cache command says
>> "(wrn) : No caches found."
>>
>> Ignite is being started with "ignite.sh config/ignite-config.xml”
>>
>> ignite-config.xml has the following content:
>>
>> -
>> 
>>
>> http://www.springframework.org/schema/beans";
>>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>>xsi:schemaLocation="
>>http://www.springframework.org/schema/beans
>>http://www.springframework.org/schema/beans/spring-beans.xsd”>
>>
>> 
>>
>>   
>>  
>> 
>> 
>> 
>> 
>>  
>>   
>>
>> 
>>
>> 
>> -
>>
>> Thanks
>>  IPVP
>>
>>
>
>
> --
> Alexey Kuznetsov
>
>


-- 
Alexey Kuznetsov

Re: ignitevisor starting the node twice

2017-05-29 Thread I PVP 
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 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 
mailto:i...@hotmail.com>> wrote:
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 configuration file and  even informing the same 
configuration file used to start ignite   ignitevisor  says:  "Ignite node 
started OK”  ,  it shows 00:00:00 uptime and the cache command says "(wrn) 
: No caches found."

Ignite is being started with "ignite.sh config/ignite-config.xml”

ignite-config.xml has the following content:

-


http://www.springframework.org/schema/beans";
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
   xsi:schemaLocation="
   http://www.springframework.org/schema/beans
   http://www.springframework.org/schema/beans/spring-beans.xsd”>


   
  
 




 
  
   



-

Thanks
 IPVP




--
Alexey Kuznetsov

Re: ignitevisor starting the node twice

2017-05-29 Thread Alexey Kuznetsov 
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  wrote:

> 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 configuration file and  even informing the
> same configuration file used to start ignite   ignitevisor  says:  "Ignite
> node started OK”  ,  it shows 00:00:00 uptime and the cache command says
> "(wrn) : No caches found."
>
> Ignite is being started with "ignite.sh config/ignite-config.xml”
>
> ignite-config.xml has the following content:
>
> -
> 
>
> http://www.springframework.org/schema/beans";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xsi:schemaLocation="
>http://www.springframework.org/schema/beans
>http://www.springframework.org/schema/beans/spring-beans.xsd”>
>
> 
>
>   
>  
> 
> 
> 
> 
>  
>   
>
> 
>
> 
> -
>
> Thanks
>  IPVP
>
>


-- 
Alexey Kuznetsov

ignitevisor starting the node twice

2017-05-27 Thread I PVP 
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 configuration file and  even informing the same 
configuration file used to start ignite   ignitevisor  says:  "Ignite node 
started OK”  ,  it shows 00:00:00 uptime and the cache command says "(wrn) 
: No caches found."

Ignite is being started with "ignite.sh config/ignite-config.xml”

ignite-config.xml has the following content:

-


http://www.springframework.org/schema/beans";
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
   xsi:schemaLocation="
   http://www.springframework.org/schema/beans
   http://www.springframework.org/schema/beans/spring-beans.xsd”>


   
  
 




 
  
   



-

Thanks
 IPVP