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

Upgrade spdy to 4.x.x and support Node v6, v8, v10 #373

Open
wants to merge 26 commits into
base: master
Choose a base branch
from

Conversation

AdamMagaluk
Copy link
Collaborator

Well it's been about two years in making but this PR allows Zetta to run on the latest version of Node.js with the spdy and ws module updated to their newest versions. Sorry for all the delay, folks.

This release adds support for the versions below and drops supports for node <= v4. v0.10, v0.12, etc.. Sorry for anyone who uses it but those versions are long retired. Fixes #336, #333 and will make progress with #337. Once merged we can move much fast to modernize the codebase.

Peering will work between old versions of zetta and this version and vise-versa.

Node.js Release Support (Node Releases)

  • v6 EoL=April 2019
  • v8 EoL=December 2019
  • v10 EoL=April 2021

v11 is going to require some work on the node-spdy front. see: spdy-http2/node-spdy#350. Or by then we can move off node-spdy in favor of the http2 core module.

Major Changes to Spdy

There were also changes in ws that broke getting the request url from the ws object. Instead we need to pass the original request to the PeerSocket.

TODO

  • - Profile CPU/Mem usage, especially with peers constantly reconnecting while cloud is subscribed to data. This caused issues in the past when the push streams were not cleaned up.
  • - Profile peer connection limits.
  • - Upgrade argo and titan to a version with no security vulnerabilities.
  • - Validate running on Beaglebone Black and Raspberry Pi.

…ient.

Fix issue with stream deduping when finding intenral remote port in the spdy internals.
Updates to the WS cause it to return a 400 instead of a 404 when
the base path does not match.
…ribe's cb

to fire a second time. Wrap cb in a once pattern.

PeerSocket guard against this.ws not being initialized when closing the connection
Our tests are scheduling async operations and calling done. We
need to clean this up but with the old version of mocha it was
exiting the test suite after all tests were done. This enforces
the old behavior.
AdamMagaluk and others added 3 commits December 11, 2018 07:10
This ensures zetta hubs running pre spdy-upgrade will be compatible
at a network level. To support `h2` we need to negotiate transport
and ALPN cannot help us.
@AdamMagaluk
Copy link
Collaborator Author

Opened a new PR since i lost access to the repo after leaving Google. #379

I also published version zetta@1.6.0 that incorporates all these changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

spdy issue
1 participant