-
Notifications
You must be signed in to change notification settings - Fork 32
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
WIP: Support HTTP2 protocol + Kinesis integration test puzzle #830
base: main
Are you sure you want to change the base?
Conversation
exceptions in toPekkoRequest should be wrapped in a future failed
SdkAsyncHttpClientH1TestSuite uses netty to simulate a server...
Unfortunately, I don't have an AWS account to test those Kinesis tests against. |
By comparing the logs of ✅
❌
Important bits:
So I think that this is a bug in http2 support of pekko-http... cc @jrudolph @raboof ? |
Is it possible to also support HTTP 1.1? It might be a nice option to be able to use a HTTP 1.1 client if there are issues with the HTTP/2 one. |
Yes, HTTP 1.1 is supported and the default except for the kinesis client is the only that "forces" the use of HTTP/2. However, before this PR the |
depends on #829
This PR adds support for HTTP/2 protocol in AWS SDK HttpClient. Since the pekko-http support for http/2 is different than for http (it only support " Host-Level" and not "Request-Level" API) the implementation is a bit more tricky.
However, I found a problem when writing integration tests: the test
KinesisITTest#list streams in parallel
runs successfully in about 2 seconds, but if I increase number of clients from 5 to 6 it gets stuck and takes more than 60s to finish...Can someone confirm they see this same behavior:
aws-spi-pekko-http/it:testOnly org.apache.pekko.stream.connectors.awsspi.kinesis.KinesisITTest -- -z "list streams"