Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
Docs Required
Description
As far as my understanding goes, it is a Docker gateway address.
Nodes see that they have this address in common, and try to use it for Communication, which leads to confusing results since 172.17.0.1 is not actually shared between them.
I think we should regard it as localhost or outright ignore it when picking address to connect to in Communication.
Attachments
Issue Links
- is related to
-
IGNITE-8985 Node segmented itself after connRecoveryTimeout
- Resolved
- links to