Re: C# client too slow to connect.

[F.D.]

Hi Yakov,

It works perfectly!

Thanks!!!

F.D.


On Thu, May 24, 2018 at 11:17 AM Yakov Zhdanov  wrote:

> Hi, slow node join is possible on windows machines which is related to
> tcp/ip stack differences from linux - windows implementation waits for the
> entire timeout which is 3000ms by defaull and linux returns immediately
> with "connection refuse".
>
> Just narrow the range - 10.200.20.90:47500..47509, try
> configuring the only 47500 port. This should help, since tcp discovery spi
> tries every address when searching for already started nodes.
>
> --Yakov
>
> 2018-05-23 10:11 GMT+03:00 F.D. :
>
>> Hi Pavel,
>>
>> Yes, but thin client cannot perform continuous query. Maybe is there an
>> alternative way to be notified when a cache change?
>>
>> On Tue, May 22, 2018 at 10:04 PM Pavel Tupitsyn 
>> wrote:
>>
>>> Hi,
>>>
>>> Have you tried Thin Client mode?
>>> https://apacheignite-net.readme.io/docs/thin-client
>>>
>>> Pavel
>>>
>>> On Tue, May 22, 2018 at 2:13 PM, F. D.  wrote:
>>>
 Hi Igor,

 it's almost the same. I'm considering startup + connection. I'm using
 Ignite 2.4.  The node excel is only client, and I have only a server node
 on an other machine in my organization, and I cannot see particular
 activity of cpu or network.

 Thanks,
F.D.

 On Tue, May 22, 2018 at 11:00 AM Igor Sapego 
 wrote:

> Hi,
>
> Try using "TcpDiscoveryStaticIpFinder" instead of
> "TcpDiscoveryMulticastIpFinder".
>
> Does it take 1 min for connection only or for start up + connection?
>
> Best Regards,
> Igor
>
> On Tue, May 22, 2018 at 11:45 AM, F. D. 
> wrote:
>
>> Hi,
>>
>> I'm trying to use Ignite to develop an internal system of data
>> contribution. To do this, I'm launching Ignite inside Excel, and I'm 
>> using
>> the C# binding.
>>
>> When try to connect it consumes a lot of time (~1 min.),  this is my
>> simple app.config:
>>
>> 
>> 
>>
>>   > type="Apache.Ignite.Core.IgniteConfigurationSection, 
>> Apache.Ignite.Core"/>
>>
>>
>>
>>
>>
>>
>>http://ignite.apache.org/schema/dotnet/IgniteConfigurationSection;
>> localhost="10.200.30.100" peerAssemblyLoadingMode="CurrentAppDomain"
>> gridName="IMIStreamer">
>>   
>>  
>>   
>>
>>   
>>
>>   
>>  
>> 
>>10.200.20.90:47500..47509
>> 
>>  
>>   
>>
>>
>>
>>   > sku=".NETFramework,Version=v4.5.2"/>
>>
>>
>> 
>>
>> Is it possibile to reduce this time of connection?
>> I've tried to use the thin client, but in this client there's no
>> continuous query (and need it, because I want to be reactive when a cache
>> change).
>>
>> Thanks in advance for your help,
>>F.D.
>>
>>
>
>>>
>

Re: C# client too slow to connect.

[Yakov Zhdanov]

Hi, slow node join is possible on windows machines which is related to
tcp/ip stack differences from linux - windows implementation waits for the
entire timeout which is 3000ms by defaull and linux returns immediately
with "connection refuse".

Just narrow the range - 10.200.20.90:47500..47509, try
configuring the only 47500 port. This should help, since tcp discovery spi
tries every address when searching for already started nodes.

--Yakov

2018-05-23 10:11 GMT+03:00 F.D. :

> Hi Pavel,
>
> Yes, but thin client cannot perform continuous query. Maybe is there an
> alternative way to be notified when a cache change?
>
> On Tue, May 22, 2018 at 10:04 PM Pavel Tupitsyn 
> wrote:
>
>> Hi,
>>
>> Have you tried Thin Client mode?
>> https://apacheignite-net.readme.io/docs/thin-client
>>
>> Pavel
>>
>> On Tue, May 22, 2018 at 2:13 PM, F. D.  wrote:
>>
>>> Hi Igor,
>>>
>>> it's almost the same. I'm considering startup + connection. I'm using
>>> Ignite 2.4.  The node excel is only client, and I have only a server node
>>> on an other machine in my organization, and I cannot see particular
>>> activity of cpu or network.
>>>
>>> Thanks,
>>>F.D.
>>>
>>> On Tue, May 22, 2018 at 11:00 AM Igor Sapego  wrote:
>>>
 Hi,

 Try using "TcpDiscoveryStaticIpFinder" instead of
 "TcpDiscoveryMulticastIpFinder".

 Does it take 1 min for connection only or for start up + connection?

 Best Regards,
 Igor

 On Tue, May 22, 2018 at 11:45 AM, F. D. 
 wrote:

> Hi,
>
> I'm trying to use Ignite to develop an internal system of data
> contribution. To do this, I'm launching Ignite inside Excel, and I'm using
> the C# binding.
>
> When try to connect it consumes a lot of time (~1 min.),  this is my
> simple app.config:
>
> 
> 
>
>    type="Apache.Ignite.Core.IgniteConfigurationSection,
> Apache.Ignite.Core"/>
>
>
>
>
>
>
>http://ignite.apache.org/schema/dotnet/
> IgniteConfigurationSection" localhost="10.200.30.100"
> peerAssemblyLoadingMode="CurrentAppDomain" gridName="IMIStreamer">
>   
>  
>   
>
>   
>
>   
>  
> 
>10.200.20.90:47500..47509
> 
>  
>   
>
>
>
>   
>
>
> 
>
> Is it possibile to reduce this time of connection?
> I've tried to use the thin client, but in this client there's no
> continuous query (and need it, because I want to be reactive when a cache
> change).
>
> Thanks in advance for your help,
>F.D.
>
>

>>

Re: C# client too slow to connect.

[F.D.]

Hi Pavel,

Yes, but thin client cannot perform continuous query. Maybe is there an
alternative way to be notified when a cache change?

On Tue, May 22, 2018 at 10:04 PM Pavel Tupitsyn 
wrote:

> Hi,
>
> Have you tried Thin Client mode?
> https://apacheignite-net.readme.io/docs/thin-client
>
> Pavel
>
> On Tue, May 22, 2018 at 2:13 PM, F. D.  wrote:
>
>> Hi Igor,
>>
>> it's almost the same. I'm considering startup + connection. I'm using
>> Ignite 2.4.  The node excel is only client, and I have only a server node
>> on an other machine in my organization, and I cannot see particular
>> activity of cpu or network.
>>
>> Thanks,
>>F.D.
>>
>> On Tue, May 22, 2018 at 11:00 AM Igor Sapego  wrote:
>>
>>> Hi,
>>>
>>> Try using "TcpDiscoveryStaticIpFinder" instead of
>>> "TcpDiscoveryMulticastIpFinder".
>>>
>>> Does it take 1 min for connection only or for start up + connection?
>>>
>>> Best Regards,
>>> Igor
>>>
>>> On Tue, May 22, 2018 at 11:45 AM, F. D.  wrote:
>>>
 Hi,

 I'm trying to use Ignite to develop an internal system of data
 contribution. To do this, I'm launching Ignite inside Excel, and I'm using
 the C# binding.

 When try to connect it consumes a lot of time (~1 min.),  this is my
 simple app.config:

 
 

   >>> type="Apache.Ignite.Core.IgniteConfigurationSection, Apache.Ignite.Core"/>






http://ignite.apache.org/schema/dotnet/IgniteConfigurationSection;
 localhost="10.200.30.100" peerAssemblyLoadingMode="CurrentAppDomain"
 gridName="IMIStreamer">
   
  
   

   

   
  
 
10.200.20.90:47500..47509
 
  
   



   >>> sku=".NETFramework,Version=v4.5.2"/>


 

 Is it possibile to reduce this time of connection?
 I've tried to use the thin client, but in this client there's no
 continuous query (and need it, because I want to be reactive when a cache
 change).

 Thanks in advance for your help,
F.D.


>>>
>

Re: C# client too slow to connect.

[Pavel Tupitsyn]

Hi,

Have you tried Thin Client mode?
https://apacheignite-net.readme.io/docs/thin-client

Pavel

On Tue, May 22, 2018 at 2:13 PM, F. D.  wrote:

> Hi Igor,
>
> it's almost the same. I'm considering startup + connection. I'm using
> Ignite 2.4.  The node excel is only client, and I have only a server node
> on an other machine in my organization, and I cannot see particular
> activity of cpu or network.
>
> Thanks,
>F.D.
>
> On Tue, May 22, 2018 at 11:00 AM Igor Sapego  wrote:
>
>> Hi,
>>
>> Try using "TcpDiscoveryStaticIpFinder" instead of
>> "TcpDiscoveryMulticastIpFinder".
>>
>> Does it take 1 min for connection only or for start up + connection?
>>
>> Best Regards,
>> Igor
>>
>> On Tue, May 22, 2018 at 11:45 AM, F. D.  wrote:
>>
>>> Hi,
>>>
>>> I'm trying to use Ignite to develop an internal system of data
>>> contribution. To do this, I'm launching Ignite inside Excel, and I'm using
>>> the C# binding.
>>>
>>> When try to connect it consumes a lot of time (~1 min.),  this is my
>>> simple app.config:
>>>
>>> 
>>> 
>>>
>>>   >> type="Apache.Ignite.Core.IgniteConfigurationSection,
>>> Apache.Ignite.Core"/>
>>>
>>>
>>>
>>>
>>>
>>>
>>>http://ignite.apache.org/schema/dotnet/
>>> IgniteConfigurationSection" localhost="10.200.30.100"
>>> peerAssemblyLoadingMode="CurrentAppDomain" gridName="IMIStreamer">
>>>   
>>>  
>>>   
>>>
>>>   
>>>
>>>   
>>>  
>>> 
>>>10.200.20.90:47500..47509
>>> 
>>>  
>>>   
>>>
>>>
>>>
>>>   
>>>
>>>
>>> 
>>>
>>> Is it possibile to reduce this time of connection?
>>> I've tried to use the thin client, but in this client there's no
>>> continuous query (and need it, because I want to be reactive when a cache
>>> change).
>>>
>>> Thanks in advance for your help,
>>>F.D.
>>>
>>>
>>

Re: C# client too slow to connect.

[F. D.]

Hi Igor,

it's almost the same. I'm considering startup + connection. I'm using
Ignite 2.4.  The node excel is only client, and I have only a server node
on an other machine in my organization, and I cannot see particular
activity of cpu or network.

Thanks,
   F.D.

On Tue, May 22, 2018 at 11:00 AM Igor Sapego  wrote:

> Hi,
>
> Try using "TcpDiscoveryStaticIpFinder" instead of
> "TcpDiscoveryMulticastIpFinder".
>
> Does it take 1 min for connection only or for start up + connection?
>
> Best Regards,
> Igor
>
> On Tue, May 22, 2018 at 11:45 AM, F. D.  wrote:
>
>> Hi,
>>
>> I'm trying to use Ignite to develop an internal system of data
>> contribution. To do this, I'm launching Ignite inside Excel, and I'm using
>> the C# binding.
>>
>> When try to connect it consumes a lot of time (~1 min.),  this is my
>> simple app.config:
>>
>> 
>> 
>>
>>   > type="Apache.Ignite.Core.IgniteConfigurationSection, Apache.Ignite.Core"/>
>>
>>
>>
>>
>>
>>
>>http://ignite.apache.org/schema/dotnet/IgniteConfigurationSection;
>> localhost="10.200.30.100" peerAssemblyLoadingMode="CurrentAppDomain"
>> gridName="IMIStreamer">
>>   
>>  
>>   
>>
>>   
>>
>>   
>>  
>> 
>>10.200.20.90:47500..47509
>> 
>>  
>>   
>>
>>
>>
>>   > sku=".NETFramework,Version=v4.5.2"/>
>>
>>
>> 
>>
>> Is it possibile to reduce this time of connection?
>> I've tried to use the thin client, but in this client there's no
>> continuous query (and need it, because I want to be reactive when a cache
>> change).
>>
>> Thanks in advance for your help,
>>F.D.
>>
>>
>

Re: C# client too slow to connect.

[Igor Sapego]

Hi,

Try using "TcpDiscoveryStaticIpFinder" instead of
"TcpDiscoveryMulticastIpFinder".

Does it take 1 min for connection only or for start up + connection?

Best Regards,
Igor

On Tue, May 22, 2018 at 11:45 AM, F. D.  wrote:

> Hi,
>
> I'm trying to use Ignite to develop an internal system of data
> contribution. To do this, I'm launching Ignite inside Excel, and I'm using
> the C# binding.
>
> When try to connect it consumes a lot of time (~1 min.),  this is my
> simple app.config:
>
> 
> 
>
>type="Apache.Ignite.Core.IgniteConfigurationSection,
> Apache.Ignite.Core"/>
>
>
>
>
>
>
>http://ignite.apache.org/schema/dotnet/
> IgniteConfigurationSection" localhost="10.200.30.100"
> peerAssemblyLoadingMode="CurrentAppDomain" gridName="IMIStreamer">
>   
>  
>   
>
>   
>
>   
>  
> 
>10.200.20.90:47500..47509
> 
>  
>   
>
>
>
>   
>
>
> 
>
> Is it possibile to reduce this time of connection?
> I've tried to use the thin client, but in this client there's no
> continuous query (and need it, because I want to be reactive when a cache
> change).
>
> Thanks in advance for your help,
>F.D.
>
>

C# client too slow to connect.

[F. D.]

Hi,

I'm trying to use Ignite to develop an internal system of data
contribution. To do this, I'm launching Ignite inside Excel, and I'm using
the C# binding.

When try to connect it consumes a lot of time (~1 min.),  this is my simple
app.config:



   
  
   

   
   
   

   http://ignite.apache.org/schema/dotnet/IgniteConfigurationSection;
localhost="10.200.30.100" peerAssemblyLoadingMode="CurrentAppDomain"
gridName="IMIStreamer">
  
 
  

  

  
 

   10.200.20.90:47500..47509

 
  
   

   
  
   



Is it possibile to reduce this time of connection?
I've tried to use the thin client, but in this client there's no continuous
query (and need it, because I want to be reactive when a cache change).

Thanks in advance for your help,
   F.D.