It is. It seems to only happen when I scale the client. Just curious. is it
possible that the client is bound to alot of address and
causing communication issues???
When I look at the topology through ignite visor I see the client has
multiple possible addresses. Is it possible to tell the client to only bind
or use one address?
--+
| xxx.xxx.0.17| 1: (@n1) | | Client| Linux amd64
3.10.0-862.14.4.el7.x86_64 | 2| | 1.00 % |
| xxx..0.1 | |
| || | xx |
|
| xxx.xxx.100.1 | |
| || | xx |
|
| xxx.xxx.100.2 | |
| || | xx |
|
| 127.0.0.1 | |
| || | xx |
|
| xxx.xxx.xxx.68 | |
| || | xx |
|
| xxx.xxx.0.1 | |
| || |
| |
| xxx.xxx.xxx.129 | |
| || |
| |
| xxx.xxx.100.3 | |
| || |
| |
++--+--+---++--+---
On Mon, 8 Jun 2020 at 17:14, akorensh wrote:
> Hello,
> It means that a node was not able to exchange message w/another node
> because of network or firewall issues. It lists the node in question inside
> the message.
>
> Check to make sure that the node is available and is in working order.
>
>
> *Failed to send DHT near response *[futId=16392, nearFutId=2,
> node=*379b18e9-a03b-4956-9184-8c514924af2a*, res=GridDhtAtomicNearResponse
> [partId=522, futId=2, primaryId=6113a59a-b087-4e70-8541-d050eea8c934,
> errs=null,
> flags=]]","stackTrace":"org.apache.ignite.IgniteCheckedException:
> Failed to send message (node may have left the grid or TCP connection
> cannot
> be established due to firewall issues) [*node=TcpDiscoveryNode
> [id=379b18e9-a03b-4956-9184-8c514924af2a, addrs=[127.0.0.1, xxx.xxx.xxx.7],
> sockAddrs=[/127.0.0.1:0, /xxx.xxx.xxx.7:0*]
>
> Thanks, Alex
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
