occurs and why?
>
>
> ERROR org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi - Failed to
> send message to remote node [node=TcpDiscoveryNode
> [id=6cc31b37-7870-413a-b75a-95b4371fc542,
> consistentId=mtnclzcom_1679291151812, addrs=ArrayList [10.233.102.12,
> 127.0
Hello,
Getting below errors continuously on Ignite node. Please help me with
explaining the below exception when it occurs and why?
ERROR org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi - Failed
to send message to remote node [node=TcpDiscoveryNode
[id=6cc31b37-7870-413a-b75a
We are using "TcpDiscoveryVmIpFinder" for connecting our 2 ignite nodes,
> running on 2 separate machines.
> But while running the ignite node are getting below error on one of the
> nodes and application and node is stopping-
> "Failed to send message to remote node"
> Belo
s stopping-
"Failed to send message to remote node"
Below are the full logs for node 1-
[14:36:32,572][SEVERE][exchange-worker-#46][TcpCommunicationSpi] Failed to
send message to remote node [node=TcpDiscoveryNode
[id=7f683a9a-afcc-4d20-95f4-855147d759fd, consistentId=DSU_A,
addrs=ArrayList
[11:32:46,462][SEVERE][sys-stripe-20-#21%SubScriptionCluster%][query]
> Failed
> to send event notification to node: 5995d947-e1f6-4210-8507-cfe7d805503e
> class org.apache.ignite.IgniteCheckedException: Failed to send message
> (node
> may have left the grid or TCP connection cannot be e
[11:32:46,462][SEVERE][sys-stripe-20-#21%SubScriptionCluster%][query] Failed
to send event notification to node: 5995d947-e1f6-4210-8507-cfe7d805503e
class org.apache.ignite.IgniteCheckedException: Failed to send message (node
may have left the grid or TCP connection cannot be established due
Hi,
1) Yes, default configuration failower SPI should by fit. Not need to
configure it specify at most cases.
2) Why are you think so? If it is, what are results when you try to execute
task, but node is out of topology?
Can you provide reproducer?
3) The information often contains in the logs
Hi,
The message appear when operation try to execute on stopping (or starting)
node.
If the message was throwed then means node out of cluster.
Tasks which will be execute in the node should be rout to another (by
failover SPI)
Please, explain where are you sow problem?
--
View this message
Hi,
Please properly subscribe to the mailing list so that the community can
receive email notifications for your messages. To subscribe, send empty
email to user-subscr...@ignite.apache.org and follow simple instructions in
the reply.
Stopping node should cancel all its tasks automatically.
Hi,
Please properly subscribe to the mailing list so that the community can
receive email notifications for your messages. To subscribe, send empty
email to user-subscr...@ignite.apache.org and follow simple instructions in
the reply.
Also, please elaborate a bit more on your use case.
Do you
Hi Val,
Thanks for clearing that up. I am catching the exception by checking the
exception message with:
if (ex.Message.Contains("Failed to send message to remote node:")) { ... }
as I only have the "catch all" ApacheIgniteException class - there seems to
be no specific
with
exception like this. Having said that, there is nothing additional required
from your side, but you can probably handle the exception.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Failed-to-send-message-to-remote-node-error-when-remote-node-has-been
aware that the
non-existent client should not receive any messages any more?
Thanks
Apache.Ignite.Core.Common.IgniteException: Java exception occurred
[class=org.apache.ignite.spi.IgniteSpiException, message=Failed to send
message to remote node: TcpDiscoveryNode
[id=58d0eb84-470d-495d-87dc
you?
>
> -Val
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Failed-to-send-message-tp3217p3311.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
l server nodes.
>
> In any case, this is just a debug message and if job stealing works for you
> as expected, I would not worry about this. If it doesn't, please describe
> the issue you have.
>
> -Val
>
>
>
> --
> View this message in context:
> http://apache-ignite-users
you
as expected, I would not worry about this. If it doesn't, please describe
the issue you have.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Failed-to-send-message-tp3217p3269.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
w this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Failed-to-send-message-tp3217p3265.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
.nabble.com/Failed-to-send-message-tp3217p3265.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
your configuration:
>
>
> class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi">
>
>
>
>
> -Val
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Failed-to-send-message-
Hi Paolo,
Can you try to disable shared memory communication and check if it helps?
Add this to your configuration:
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Failed-to-send-message-tp3217p3229.html
Sent from the Apache Ignite
20 matches
Mail list logo
