Peer-to-peer connections use the --server-port causing the server to hang during startup

[Jakov Varenina]

Hi devs,


We have noticed that some peer-to-peer connections use ports outside the 
range defined by the membership-port-range (41000-61000) parameter:



[vm1] membership-port-range=41000-61000

[vm1] [debug 2022/05/02 11:15:57.968 CEST server-1 Connection(1)-192.168.1.36> tid=0x1a] starting peer-to-peer handshake on 
socket Socket[addr=/192.168.1.36,port=49913,*localport=37392*]



Is it expected that peer-to-peer connections use ports outside the above 
range?



Also, due to the above behavior, the following bug occurs: 
https://issues.apache.org/jira/browse/GEODE-10268 




Best Regards,

Jakov

distributedTests should go in src/distributedTest

[Kirk Lund]

Just a quick reminder that all distributedTests should go in
src/distributedTest.

A test should only be considered an acceptanceTest if it uses GfshRule to
launch the locator and server processes, and it should only use User APIs
for everything (configuration, initiating operations and validating
results). If the test cannot be performed without resorting to using
VM.invoke or something like that to poke at the process, then please just
make it a distributedTest rather than adding it to src/acceptanceTest.

Thanks,
Kirk

Re: Peer-to-peer connections use the --server-port causing the server to hang during startup

[Dan Smith]

I think the membership-port-range determines the port that the server side of 
the TCP socket is listening on.

What I see in your log statement is the port number of the client side of the 
socket (where it says localport=37392). The port for the client side of a 
socket comes from the ephemeral port range configured on your OS - usually 
32768–60999 in linux.

https://en.wikipedia.org/wiki/Ephemeral_port

-Dan

From: Jakov Varenina 
Sent: Monday, May 2, 2022 5:49 AM
To: dev@geode.apache.org 
Subject: Peer-to-peer connections use the --server-port causing the server to 
hang during startup

⚠ External Email

Hi devs,


We have noticed that some peer-to-peer connections use ports outside the
range defined by the membership-port-range (41000-61000) parameter:


[vm1] membership-port-range=41000-61000

[vm1] [debug 2022/05/02 11:15:57.968 CEST server-1  tid=0x1a] starting peer-to-peer handshake on
socket Socket[addr=/192.168.1.36,port=49913,*localport=37392*]


Is it expected that peer-to-peer connections use ports outside the above
range?


Also, due to the above behavior, the following bug occurs:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FGEODE-10268&data=05%7C01%7Cdasmith%40vmware.com%7Cf61b0d0e14774737c7ee08da2c3a2e72%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637870925648179770%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VJQGl83OSKWTWwn%2FR7bdJorcQqAP3goEPz4cddHHgZM%3D&reserved=0



Best Regards,

Jakov



⚠ External Email: This email originated from outside of the organization. Do 
not click links or open attachments unless you recognize the sender.