You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by ozgurnevres <oz...@gmail.com> on 2017/04/05 09:54:57 UTC
Asp.net client reconnect problem
Hi,
I am running Ignite on asp.net as a client node. I have also a server node
as console application.
M problem is:
1- When I stop the server node when asp.net client node is connected, it
fires first "ClientDisconnected" event. Then, a few seconds later fires
"ClientReconnected" event. Why? The server is still down.
2- Then I restarting the server node. The client never reconnects again. In
the server's console screen, the number of clients remains 0.
Am I missing something? How can I correctly handle the "server temporarily
down" or "server is restarting" case?
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Asp-net-client-reconnect-problem-tp11735.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Asp.net client reconnect problem
Posted by ozgurnevres <oz...@gmail.com>.
And yes, I am sure there's no other server node. (Topology shows 1 server ven
I restart the server)
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Asp-net-client-reconnect-problem-tp11735p11751.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Asp.net client reconnect problem
Posted by ozgurnevres <oz...@gmail.com>.
Hi, Pavel
The steps are below:
1- I am starting server node.
2- Then starting asp.net client node.
3- Querying database. Works perfect.
4- Stopping server node. Ignite fires ClientDisconnected as one expected.
5- A few seconds later, while server is still down, Ignite fires
ClientReconnected event (this is confusing, I don't know why).
6- After ClientReconnected fired, I restart the server node.
7- Nothing happens. It never fires ClientReconnected again.
8- When I query database in this situation, I get "Grid is in invalid state
to perform this operation. It either not started yet or has already being or
have stopped" exception.
I didn't implemented the logging yet, I'll read how to do it and then I'll
send you the logs.
Thanks
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Asp-net-client-reconnect-problem-tp11735p11750.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Asp.net client reconnect problem
Posted by Pavel Tupitsyn <pt...@apache.org>.
> Grid is in invalid state to perform this operation
When does this happen? Can you provide more details or a project to
reproduce?
Are you sure you don't call Ignition.Stop somewhere?
On Wed, Apr 5, 2017 at 2:08 PM, ozgurnevres <oz...@gmail.com> wrote:
> While we send a query to our cluster, We get the following error message
> from
> asp.net client node
>
> "Grid is in invalid state to perform this operation. It either not started
> yet or has already being or have stopped [gridName=myGrid1, state=STOPPED]"
>
> Then we restart every thing on client node(app pool etc) and everything
> works fine.
> After i got this error, the client never connects again.
> Should I handle this error and how?
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Asp-net-client-reconnect-problem-tp11735p11743.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
Re: Asp.net client reconnect problem
Posted by ozgurnevres <oz...@gmail.com>.
While we send a query to our cluster, We get the following error message from
asp.net client node
"Grid is in invalid state to perform this operation. It either not started
yet or has already being or have stopped [gridName=myGrid1, state=STOPPED]"
Then we restart every thing on client node(app pool etc) and everything
works fine.
After i got this error, the client never connects again.
Should I handle this error and how?
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Asp-net-client-reconnect-problem-tp11735p11743.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Asp.net client reconnect problem
Posted by Pavel Tupitsyn <pt...@apache.org>.
Yes, this fix will be included in upcoming Ignite 2.0.
You can also download recent nightly build of NuGet package:
https://cwiki.apache.org/confluence/display/IGNITE/Nightly+Builds
On Fri, Apr 7, 2017 at 2:43 PM, ozgurnevres <oz...@gmail.com> wrote:
> I think you mean the source code on github, did I get it right?
>
> Will this fix be included in the future updates of the Ignite nuget
> package?
> thanks
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Asp-net-client-reconnect-problem-tp11735p11808.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
Re: Asp.net client reconnect problem
Posted by ozgurnevres <oz...@gmail.com>.
I think you mean the source code on github, did I get it right?
Will this fix be included in the future updates of the Ignite nuget package?
thanks
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Asp-net-client-reconnect-problem-tp11735p11808.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Asp.net client reconnect problem
Posted by Nikolai Tikhonov <nt...@apache.org>.
Seems it related with https://issues.apache.org/jira/browse/IGNITE-4473
issue. This fixed in master you can try to build ignite from master and
check.
On Thu, Apr 6, 2017 at 3:51 PM, Alper Tekinalp <al...@evam.com> wrote:
> Hi.
>
> All segmentation issues that I encountered were due to long GC pauses.
> Maybe that can be a clue.
>
> Regards.
>
> On Thu, Apr 6, 2017 at 3:40 PM, Pavel Tupitsyn <pt...@apache.org>
> wrote:
>
>> Igniters, there is a node segmentation in the log, can someone with
>> experience in this area step in?
>> This is not related to ASP.NET and .NET, I believe.
>>
>> On Thu, Apr 6, 2017 at 1:45 PM, ozgurnevres <oz...@gmail.com>
>> wrote:
>>
>>> Any suggestion? :(
>>>
>>>
>>>
>>> --
>>> View this message in context: http://apache-ignite-users.705
>>> 18.x6.nabble.com/Asp-net-client-reconnect-problem-tp11735p11772.html
>>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>>
>>
>>
>
>
> --
> Alper Tekinalp
>
> Software Developer
> Evam Streaming Analytics
>
> Atatürk Mah. Turgut Özal Bulv.
> Gardenya 5 Plaza K:6 Ataşehir
> 34758 İSTANBUL
>
> Tel: +90 216 455 01 53 Fax: +90 216 455 01 54
> www.evam.com.tr
> <http://www.evam.com>
>
Re: Asp.net client reconnect problem
Posted by Alper Tekinalp <al...@evam.com>.
Hi.
All segmentation issues that I encountered were due to long GC pauses.
Maybe that can be a clue.
Regards.
On Thu, Apr 6, 2017 at 3:40 PM, Pavel Tupitsyn <pt...@apache.org> wrote:
> Igniters, there is a node segmentation in the log, can someone with
> experience in this area step in?
> This is not related to ASP.NET and .NET, I believe.
>
> On Thu, Apr 6, 2017 at 1:45 PM, ozgurnevres <oz...@gmail.com>
> wrote:
>
>> Any suggestion? :(
>>
>>
>>
>> --
>> View this message in context: http://apache-ignite-users.705
>> 18.x6.nabble.com/Asp-net-client-reconnect-problem-tp11735p11772.html
>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>
>
>
--
Alper Tekinalp
Software Developer
Evam Streaming Analytics
Atatürk Mah. Turgut Özal Bulv.
Gardenya 5 Plaza K:6 Ataşehir
34758 İSTANBUL
Tel: +90 216 455 01 53 Fax: +90 216 455 01 54
www.evam.com.tr
<http://www.evam.com>
Re: Asp.net client reconnect problem
Posted by Pavel Tupitsyn <pt...@apache.org>.
Igniters, there is a node segmentation in the log, can someone with
experience in this area step in?
This is not related to ASP.NET and .NET, I believe.
On Thu, Apr 6, 2017 at 1:45 PM, ozgurnevres <oz...@gmail.com> wrote:
> Any suggestion? :(
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Asp-net-client-reconnect-problem-tp11735p11772.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
Re: Asp.net client reconnect problem
Posted by ozgurnevres <oz...@gmail.com>.
Any suggestion? :(
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Asp-net-client-reconnect-problem-tp11735p11772.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Asp.net client reconnect problem
Posted by ozgurnevres <oz...@gmail.com>.
log.txt <http://apache-ignite-users.70518.x6.nabble.com/file/n11752/log.txt>
Hi Pavel,
The log file (after ClientReconnected is fired while server is still down)
is attached.
thanks
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Asp-net-client-reconnect-problem-tp11735p11752.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Asp.net client reconnect problem
Posted by Pavel Tupitsyn <pt...@apache.org>.
> a few seconds later fires "ClientReconnected" event
This is suspicious. Are you sure no other nodes are running on your machine
or in the local network?
Can you attach the log?
I have tested this exact scenario today (ASP.NET runs Ignite in client
mode, server is a standalone executable) and it works as expected.
On Wed, Apr 5, 2017 at 12:54 PM, ozgurnevres <oz...@gmail.com> wrote:
> Hi,
> I am running Ignite on asp.net as a client node. I have also a server node
> as console application.
> M problem is:
> 1- When I stop the server node when asp.net client node is connected, it
> fires first "ClientDisconnected" event. Then, a few seconds later fires
> "ClientReconnected" event. Why? The server is still down.
> 2- Then I restarting the server node. The client never reconnects again. In
> the server's console screen, the number of clients remains 0.
>
> Am I missing something? How can I correctly handle the "server temporarily
> down" or "server is restarting" case?
>
>
>
>
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Asp-net-client-reconnect-problem-tp11735.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>