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

websocket: add reuseport support #2261

Closed

Conversation

chaitanyaprem
Copy link
Contributor

@chaitanyaprem chaitanyaprem commented Apr 26, 2023

Implemented reuse-port capability for websocket transport #1435 using the existing net/reuseport transport and libp2p/go-reuseport.

In order to utilize REUSEPORT, reuseport option has to be passed while creating the websocket transport.
This would allow for multiple threads/routines to listen on same IP/port combination.

Included a test that would verify reuseport by running 2 go-routines that would listen on same address and accept connections from 4 different clients.

Reran the existing test-suite for the websocket package to ensure no other tests fail.

Note: Tested the new changes in ubuntu-20.04 and windows-11 environment.

@marten-seemann marten-seemann self-requested a review April 26, 2023 14:58
Copy link
Contributor

@marten-seemann marten-seemann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your PR! This mostly looks good, just a few comments.

p2p/transport/websocket/websocket.go Outdated Show resolved Hide resolved
p2p/transport/websocket/websocket.go Outdated Show resolved Hide resolved
p2p/transport/websocket/websocket_test.go Outdated Show resolved Hide resolved
@marten-seemann marten-seemann linked an issue Apr 27, 2023 that may be closed by this pull request
@marten-seemann marten-seemann changed the title feat: add reuseport support for websocket transport websocket: add reuseport support Apr 27, 2023
@chaitanyaprem
Copy link
Contributor Author

Thank you for your PR! This mostly looks good, just a few comments.

You are welcome. Pushed new commits addressing your review comments.

@chaitanyaprem
Copy link
Contributor Author

@marten-seemann please approve the workflows post which this can be merged.

Copy link
Contributor

@marten-seemann marten-seemann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @chaitanyaprem! The code looks good to me, but I'm a bit confused with the test case.

Unfortunately, we just switched back to the Gorilla WebSocket library (#2280). This is creating merge conflicts with this PR. Would you mind rebasing this PR on top of the current master?

p2p/transport/websocket/websocket_test.go Outdated Show resolved Hide resolved
p2p/transport/websocket/websocket_test.go Outdated Show resolved Hide resolved
@chaitanyaprem
Copy link
Contributor Author

Thank you @chaitanyaprem! The code looks good to me, but I'm a bit confused with the test case.

Unfortunately, we just switched back to the Gorilla WebSocket library (#2280). This is creating merge conflicts with this PR. Would you mind rebasing this PR on top of the current master?

Will resolve and push updated ones.

Listen on unspecified port.
Verify that client connections are distributed amongst multiple listeners.
@chaitanyaprem
Copy link
Contributor Author

Pushed updated changes as per review comments.

Copy link

@Maelkum Maelkum left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice PR! (commenting as an outsider)

Q: This PR adds the ability to listen on the same port by multiple parties. The TCP implementation for reuseport will also try to use listening ports also for dialing. This is not handled in this PR, is that right?

p2p/transport/websocket/websocket.go Outdated Show resolved Hide resolved
p2p/transport/websocket/websocket_test.go Outdated Show resolved Hide resolved
p2p/transport/websocket/websocket_test.go Outdated Show resolved Hide resolved
p2p/transport/websocket/websocket_test.go Outdated Show resolved Hide resolved
p2p/transport/websocket/websocket_test.go Outdated Show resolved Hide resolved
p2p/transport/websocket/websocket_test.go Outdated Show resolved Hide resolved
p2p/transport/websocket/websocket_test.go Outdated Show resolved Hide resolved
@chaitanyaprem
Copy link
Contributor Author

Nice PR! (commenting as an outsider)

Q: This PR adds the ability to listen on the same port by multiple parties. The TCP implementation for reuseport will also try to use listening ports also for dialing. This is not handled in this PR, is that right?

Thanks @Maelkum for your comments. Addressed all the others.
You are right that reuseport is not added for dialing as it doesn't seem straight-forward with gorilla websocket.
Will see how to get around that.

@chaitanyaprem
Copy link
Contributor Author

Wow, this is surprising that load balancing across multiple listeners is not functioning on windows as well as Mac even-though 2 sockets are allowed to listen on same address+port.

Wrt Windows, i found this ref which does not guarantee the behaviour of SO_REUSEADDR.
Quote from windows ref is not very clear wrt load balancing.
For example, if all of the sockets on the same port provide TCP service, any incoming TCP connection requests over the port cannot be guaranteed to be handled by the correct socket — the behavior is non-deterministic.

Has the TCP reuse port been tested for load balancing?

Note: While going through the web searching for expected behaviour for these socket options, noticed that for FreeBSD based systems in order for load balancing to be supported an additional option has to be set SO_REUSEPORT_LB, Ref. This is something to be explored and added to the reuseport package

Will update once i investigate further.

chore: reuseport test script-Skipping connection load balancing check for architectures other than linux as it is not gauranteed.
@chaitanyaprem
Copy link
Contributor Author

chaitanyaprem commented May 26, 2023

Update on further investigation, looks like macOS also doesn't support load balancing across listeners.
Few refs:
Ref1
Ref2

So, for now I have skipped checking for load balancing of connections for any platform other than linux in the test script.
Raised an enhancement issue on the go-reuseport repo libp2p/go-reuseport#105 in order to enable LB functionality for FREEBSD based systems by setting SO_REUSEPORT_LB as indicated above.

@chaitanyaprem
Copy link
Contributor Author

chaitanyaprem commented May 30, 2023

Pushed changes to reuse port in case of dailing.
Note that in case of wss with SNI, reuse port cannot be used as the dail function has already been replaced in order to not resolve address and directly do a TCP Dial.

@chaitanyaprem
Copy link
Contributor Author

@marten-seemann @MarcoPolo All required changes and review comments have been addressed.
Please go ahead and merge this PR if nothing else is required.

@sukunrt sukunrt mentioned this pull request Aug 7, 2023
21 tasks
@marten-seemann
Copy link
Contributor

@chaitanyaprem The WebSocket tests are failing on CI. Can you please take a look?

@marten-seemann marten-seemann mentioned this pull request Aug 15, 2023
23 tasks
@chaitanyaprem
Copy link
Contributor Author

Surprisingly the test is successful now, i ran it on a local ubuntu vm (Ubuntu 22.04.3 LTS) as well and there also tests are successful.

It is hard to determine whether some other change fixed the issue or is the test just flaky.

@marten-seemann
Copy link
Contributor

I reran the test suite and it's failing again. We can't introduce any flaky tests, please make sure it consistently passes (you can run the test suite with -count=1000 locally).

@chaitanyaprem
Copy link
Contributor Author

I reran the test suite and it's failing again. We can't introduce any flaky tests, please make sure it consistently passes (you can run the test suite with -count=1000 locally).

Ran it 1000 times and it fails sometimes.
Commenting the additional load balancing check for now. Looks like linux is doesn't gaurantee it.

@p-shahi
Copy link
Member

p-shahi commented Aug 25, 2023

@sukunrt is gonna help take this over the finish line in time for the v0.31 release @chaitanyaprem

Copy link
Member

@sukunrt sukunrt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have a couple of other nits, but let's get the dial side to reuse the port we are listening on first.

p2p/transport/websocket/websocket_test.go Outdated Show resolved Hide resolved
Comment on lines +60 to +61
nl, err = reuseport.Listen(lnet, lnaddr)
if err != nil {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We want to use the transport's reuseTransport field. Otherwise this will never reuse the port we're listening on when dialing. I guess you can pass them in to newListener.

Also add a test that we are reusing port when dialing.

dialer.NetDial = func(network, address string) (net.Conn, error) {
return t.reuseTransport.DialContext(ctx, raddr)
}
}
if isWss {
sni := ""
sni, err = raddr.ValueForProtocol(ma.P_SNI)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@p-shahi p-shahi mentioned this pull request Aug 31, 2023
25 tasks
@sukunrt
Copy link
Member

sukunrt commented Sep 15, 2023

@chaitanyaprem just checking in. Let me know if you have any questions here. I'm available in filecoin slack(link in repo README).

@chaitanyaprem
Copy link
Contributor Author

@chaitanyaprem just checking in. Let me know if you have any questions here. I'm available in filecoin slack(link in repo README).

Got little busy with other work and hence not able to take a look at this.
Thanks for providing a channel to reach out, will do once i start working on this again.

@sukunrt
Copy link
Member

sukunrt commented Sep 26, 2023

Thanks for the update @chaitanyaprem

@marten-seemann marten-seemann added the need/author-input Needs input from the original author label Oct 20, 2023
@Maelkum
Copy link

Maelkum commented Feb 8, 2024

Hi guys! I hope this is not me being rude.. At a similar time when this PR was opened, I played around with implementing a similar thing. I rebased those changes to sync with the latest master (at the time this repo used nhooyr.io/websocket).

Tested it mostly in the listen => dial scenario, compared to multiple listens.

Since this PR is open for a while now, I figured I'd throw the link here. Feel free to cherry pick any piece of code out of there if it's useful. Hope this isn't bad manners!

Maelkum#1

@sukunrt
Copy link
Member

sukunrt commented Feb 21, 2024

Thanks @Maelkum. This PR has been dormant for a while so I think it's okay. Do you want to open a new PR or take over this one?
@chaitanyaprem is it fine if @Maelkum continues the work here?

@chaitanyaprem
Copy link
Contributor Author

Thanks @Maelkum. This PR has been dormant for a while so I think it's okay. Do you want to open a new PR or take over this one? @chaitanyaprem is it fine if @Maelkum continues the work here?

Thanks @Maelkum
Feel free to takeover, have not been able to get to this one myself.

@Maelkum
Copy link

Maelkum commented Feb 24, 2024

@sukunrt @chaitanyaprem
Thanks guys! I'll open a new PR and link this one there, I think it will be tidier that way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need/author-input Needs input from the original author
Projects
None yet
Development

Successfully merging this pull request may close these issues.

websocket: use reuseport
6 participants