[
https://issues.apache.org/jira/browse/IGNITE-14909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17364244#comment-17364244
]
Alexey Scherbakov commented on IGNITE-14909:
--------------------------------------------
[~apolovtcev]
It seems we have two issues here.
1) Mismatch in scalecube cluster node binding address and raft rpc node
endpoint configuration, caused by some specific network configuration.
My local pc and TC doesn't suffer from this. Looks like you have fixed this
problem, but I'm not 100% sure.
The correct fix probably should check all possible addresses in
org.apache.ignite.network.TopologyService#getByAddress, because scalecube node
can bind to multiple addresses.
2) The very rare issue with "Address already in use", caused by quick node
restarts.
I've just got it in my test running in the endless loop. Seems it's not fixed
yet. Adding a small delay between tests can help to mitigate this problem.
You can try to reproduce it by running IgniteRpcTest many times on TC.
So, I'm ok with the current fix for local failures.
> IgniteRpcTest fails locally
> ---------------------------
>
> Key: IGNITE-14909
> URL: https://issues.apache.org/jira/browse/IGNITE-14909
> Project: Ignite
> Issue Type: Bug
> Reporter: Ivan Bessonov
> Assignee: Aleksandr Polovtcev
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha3
>
> Attachments: IgniteRpcTest.log
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> See attached log file.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
