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

Jump to bottom

Enhancement: Expose TcpIpJoiner.MAX_PORT_TRIES as a configurable property #5062

Closed
mdogan opened this issue Apr 14, 2015 · 0 comments · Fixed by #5175
Closed

Enhancement: Expose TcpIpJoiner.MAX_PORT_TRIES as a configurable property #5062

mdogan opened this issue Apr 14, 2015 · 0 comments · Fixed by #5175
Labels
Source: Internal PR or issue was opened by an employee Team: Core Type: Enhancement
Milestone
3.4.3

Comments

@mdogan
Copy link
Contributor

mdogan commented Apr 14, 2015

Currently Hazelcast tries at most 3 incremental ports when tcp-ip joiner is used and no explicit port is defined in member-list. See

hazelcast/hazelcast/src/main/java/com/hazelcast/cluster/impl/TcpIpJoiner.java

Line 396 in 6881192

int count = portIsDefined ? 1 : MAX_PORT_TRIES;

This TcpIpJoiner.MAX_PORT_TRIES compile time constant can be exposed to allow searching more ports.

See Zendest ticket: 838
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Source: Internal PR or issue was opened by an employee Team: Core Type: Enhancement
Projects
None yet
Milestone
3.4.3
Development

Successfully merging a pull request may close this issue.

Exposed TcpIpJoiner.MAX_PORT_TRIES as a configurable system property mdogan/hazelcast
2 participants
@mdogan @mmedenjak