-
Notifications
You must be signed in to change notification settings - Fork 25k
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
[CI] Netty4HttpPipeliningHandlerTests testLargeFullResponsesAreSplit failing #104728
Labels
:Distributed Coordination/Network
Http and internode communication implementations
low-risk
An open issue or test failure that is a low risk to future releases
Team:Distributed (Obsolete)
Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination.
>test-failure
Triaged test failures from CI
Comments
mark-vieira
added
:Distributed Coordination/Network
Http and internode communication implementations
>test-failure
Triaged test failures from CI
labels
Jan 24, 2024
elasticsearchmachine
added
blocker
Team:Distributed (Obsolete)
Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination.
labels
Jan 24, 2024
Pinging @elastic/es-distributed (Team:Distributed) |
Muted on @DaveCTurner looks like you recently authored this test, mind taking a look? |
ywangd
added a commit
to ywangd/elasticsearch
that referenced
this issue
Jan 25, 2024
Lower the upper bound of large response size from 2 times of suggestedMaxAllocationSize to 1.5 so that it be sent over with 3 messages. This is because the split threshold is 0.99 of suggestedMaxAllocationSize. Resolves: elastic#104728
ywangd
added
low-risk
An open issue or test failure that is a low risk to future releases
and removed
blocker
labels
Jan 25, 2024
It is a test issue. I raised #104729 |
ywangd
added a commit
that referenced
this issue
Jan 25, 2024
Lower the upper bound of large response size from 2 times of suggestedMaxAllocationSize to 1.5 so that it be sent over with 3 messages. This is because the split threshold is 0.99 of suggestedMaxAllocationSize. Resolves: #104728
henningandersen
pushed a commit
to henningandersen/elasticsearch
that referenced
this issue
Jan 25, 2024
henningandersen
pushed a commit
to henningandersen/elasticsearch
that referenced
this issue
Jan 25, 2024
Lower the upper bound of large response size from 2 times of suggestedMaxAllocationSize to 1.5 so that it be sent over with 3 messages. This is because the split threshold is 0.99 of suggestedMaxAllocationSize. Resolves: elastic#104728
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Distributed Coordination/Network
Http and internode communication implementations
low-risk
An open issue or test failure that is a low risk to future releases
Team:Distributed (Obsolete)
Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination.
>test-failure
Triaged test failures from CI
This looks to have been added in #104642 and reproduced locally for me.
Build scan:
https://gradle-enterprise.elastic.co/s/jixspoaeb4qoe/tests/:modules:transport-netty4:test/org.elasticsearch.http.netty4.Netty4HttpPipeliningHandlerTests/testLargeFullResponsesAreSplit
Reproduction line:
Applicable branches:
main
Reproduces locally?:
Yes
Failure history:
Failure dashboard for
org.elasticsearch.http.netty4.Netty4HttpPipeliningHandlerTests#testLargeFullResponsesAreSplit
Failure excerpt:
The text was updated successfully, but these errors were encountered: