Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

problem on using domain instead of ip address #230

Closed
enesakar opened this issue Aug 5, 2012 · 2 comments

Comments

Projects
None yet
4 participants
@enesakar
Copy link
Member

commented Aug 5, 2012

when domain is used TCP/IP network , REDO_MEMBER_UNKNOWN is thrown

details:
https://groups.google.com/forum/#!msg/hazelcast/VfzJy27G5B0/vTSvV2MCejgJ

@cherron

This comment has been minimized.

Copy link

commented Nov 14, 2012

In commit id 865e2c9, ConnectionManager began to defend exact equality of the local node's address with the targeted endpoint. Why is this necessary? It actively works against scenarios where hostnames or IPs are changing in a cluster. Its another obstacle to rolling upgrades. Could this check be made optional, or logged as a warning, but allow to proceed?

@MrEasy

This comment has been minimized.

Copy link
Contributor

commented Jun 26, 2014

This still is an issue in Hazelcast 3.2.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.