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

Enable HTTP/2 for internal communication by default #23857

Merged
merged 15 commits into from
Oct 23, 2024

Conversation

wendigo
Copy link
Contributor

@wendigo wendigo commented Oct 21, 2024

Description

Additional context and related issues

Related to #22271 and #21793

Release notes

( ) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
(x) Release notes are required, with the following suggested text:

## General
* Enable HTTP/2 for internal communication by default. ({issue}`issuenumber`)

@cla-bot cla-bot bot added the cla-signed label Oct 21, 2024
@wendigo wendigo force-pushed the serafin/simplify-pages-exchange branch 3 times, most recently from 0bc3f9d to be4d7c8 Compare October 22, 2024 09:28
This was used in a single place so it's better to inline it
As it's decoupled from the processing logic so this could race. When timeout is applied on the future,
there is a single place that defines a state of the processing.
@wendigo wendigo force-pushed the serafin/simplify-pages-exchange branch from be4d7c8 to dded9b6 Compare October 22, 2024 09:35
@@ -93,8 +85,6 @@ public Response toResponse(Throwable throwable)
.build();
case WebApplicationException webApplicationException -> webApplicationException.getResponse();
default -> {
log.warn(throwable, "Request failed for %s", request.getRequestURI());
Copy link
Member

Choose a reason for hiding this comment

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

"Request could be already recycled"

Is that really valid? Was the log message not useful?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes. The ThrowableMapper can be called when the response write has failed - in this case, mapping of the exception to the response doesn't make sense at all as you won't be able to write it anyway

@wendigo wendigo changed the title Simplify page serialization on the wire + other http fixes Enable HTTP/2 for internal communication by default Oct 22, 2024
@wendigo wendigo force-pushed the serafin/simplify-pages-exchange branch from dded9b6 to e832e9f Compare October 22, 2024 10:59
@wendigo
Copy link
Contributor Author

wendigo commented Oct 22, 2024

Supersedes #22461

Copy link
Member

@losipiuk losipiuk left a comment

Choose a reason for hiding this comment

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

LGTM - but I want some other people to take a look too.
@electrum, @Praveen2112, @hashhar, @findepi

@wendigo wendigo force-pushed the serafin/simplify-pages-exchange branch 2 times, most recently from 9d7f941 to 2c174ce Compare October 22, 2024 18:36
@wendigo wendigo force-pushed the serafin/simplify-pages-exchange branch from f0b58fa to e832e9f Compare October 22, 2024 21:20
@wendigo wendigo merged commit a7216ec into master Oct 23, 2024
117 checks passed
@wendigo wendigo deleted the serafin/simplify-pages-exchange branch October 23, 2024 05:20
@github-actions github-actions bot added this to the 463 milestone Oct 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

4 participants