Skip to content
This repository has been archived by the owner on Dec 9, 2024. It is now read-only.

AWS discovery does not have member port configuration for clients #3

Closed
sertugkaya opened this issue Mar 22, 2016 · 1 comment
Closed

AWS discovery does not have member port configuration for clients #3

sertugkaya opened this issue Mar 22, 2016 · 1 comment
Labels
Type: Enhancement
Milestone
2.0.0

Comments

@sertugkaya
Copy link

Currently, with version 3.6 using aws discovery, clients only try to connect port 5701, 5702 and 5703. If one configures members on different ports than these, clients are not able to find members on aws.
@sertugkaya sertugkaya mentioned this issue Mar 22, 2016
Closed
@emrahkocaman
Copy link
Contributor

@sertugkaya hazelcast-aws plugin now implements Discovery SPI. You can define the member port using hz-port property. See documentation for details.
This will be available with the next release of hazelcast-aws.

@emrahkocaman emrahkocaman added this to the 1.1.2 milestone Apr 24, 2017
@emrahkocaman emrahkocaman mentioned this issue Apr 24, 2017
Closed
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Assignees
No one assigned
Labels
Type: Enhancement
Projects
None yet
Milestone
2.0.0
Development

No branches or pull requests
2 participants
@emrahkocaman @sertugkaya