Versions Compared

Old Version 13

changes.mady.by.user Ernest Burghardt

Saved on

compared with

New Version 14

changes.mady.by.user Dan Smith

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

There is an issue here with the need to listen on two separate ports and distribute both ports to other members. Currently, we distribute the jgroups UDP server port as part of the InternalDistributedMember. InternalDistributedMembers are sent as part of view messages and find coordinator requests to the locator. That allows all members to discover the listening port of other members (see GMSJoinLeave message sequence diagrams). We need to distribute the new tcp port as well. There are a couple options we are evaluating:

  1. Bind to the same port for both UDP and TCP traffic. Newer members would use TCP. This would require finding an available port with both protocols.
  2. Add another port field to InternalDistributedMember
  3. Pass the new membership port around outside of InternalDistributedMember. This would probably involve sending it part of the FindCoordinatorResponse, as well as including it in the GMSMembershipView.

...