Re: ignite messaging disconnection behaviour

[dkarachentsev]

Hi Kevin,

Unfortunately community decided to leave it as is, because messages are sent
asynchronously by design, but connection establishing is not. That was made
intentionally and user should take it into account and resolve depending on
concrete situation.

Thanks!

-Dmitry.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/ignite-messaging-disconnection-behaviour-tp11218p11658.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: ignite messaging disconnection behaviour

[kfeerick]

Hi Dmitry,
Did you have a chance to raise the ticket for this issue? If so can you
supply a JIRA ref?

Cheers,
Kevin



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/ignite-messaging-disconnection-behaviour-tp11218p11648.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: ignite messaging disconnection behaviour

[dkarachentsev]

Hi Kevin,

It seems that async mode has no effect for message sending, I've wrote a
suggestion to fix this in dev list. But for now you could delegate message
sending to separate thread just to release your main thread.
I'll send follow up message to you with ticket number, if or when it will be
opened.

Thanks!

-Dmitry.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/ignite-messaging-disconnection-behaviour-tp11218p11418.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: ignite messaging disconnection behaviour

[kfeerick]

Hi Dmitry,
Thanks for the suggestion. It does not seem to make a difference and the
calling thread still seems to block before an exception gets thrown from the
TcpCommunicationSpi

It appears you can tweak how quickly the exception gets throws by adjusting
the failureDetectionTimeout on the cache configuration however this is not
that desirable as we run across a variety of network topologies and don't
want to tune this value for all our cache instances. We really do want to
fire and forget if someone is listening, great. If they're not no problem
either.

I've written a quick example to demonstrate the behaviour - appreciate if
you could take a look and advise

Cheers
messaging-reproducer.zip
<http://apache-ignite-users.70518.x6.nabble.com/file/n11329/messaging-reproducer.zip>
  





--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/ignite-messaging-disconnection-behaviour-tp11218p11329.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: ignite messaging disconnection behaviour

[dkarachentsev]

Hi Kevin,

You may use IgniteMessaging in async mode:
IgniteMessaging msg = ignite.message().withAsync();
msg.sendOrdered("my-topic", objectToSend, 1);

In that case you'll not wait for sending message and reconnections in if
there was a failure.

-Dmitry.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/ignite-messaging-disconnection-behaviour-tp11218p11311.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

ignite messaging disconnection behaviour

[kfeerick]

node: TcpDiscoveryNode [id=613517f0-9534-46e3-bbe7-eb5ed1515b27,
addrs=[0:0:0:0:0:0:0:1, 10.1.1.15, 127.0.0.1, 172.27.236.2,
2001:0:9d38:6abd:18fe:1bb0:f5fe:fef0], sockAddrs=[/172.27.236.2:47501,
/2001:0:9d38:6abd:18fe:1bb0:f5fe:fef0:47501, A0004.lan/10.1.1.15:47501,
/0:0:0:0:0:0:0:1:47501, /127.0.0.1:47501], discPort=47501, order=2,
intOrder=2, lastExchangeTime=1489622741577, loc=false,
ver=1.8.0#20161205-sha1:9ca40dbe, isClient=false]
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2017)
~[ignite-core-1.8.0.jar:1.8.0]
at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:1955)
~[ignite-core-1.8.0.jar:1.8.0]
at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1148)
~[ignite-core-1.8.0.jar:1.8.0]
at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1571)
~[ignite-core-1.8.0.jar:1.8.0]
at
org.apache.ignite.internal.managers.communication.GridIoManager.sendOrderedMessage(GridIoManager.java:1315)
~[ignite-core-1.8.0.jar:1.8.0]
at
org.apache.ignite.internal.managers.communication.GridIoManager.sendUserMessage(GridIoManager.java:1453)
~[ignite-core-1.8.0.jar:1.8.0]
at
org.apache.ignite.internal.IgniteMessagingImpl.sendOrdered(IgniteMessagingImpl.java:140)
~[ignite-core-1.8.0.jar:1.8.0]



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/ignite-messaging-disconnection-behaviour-tp11218.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.