Comments (3)
I'm going to close this out until we have more info here. It's possible our tests aren't cleaning up properly.
from grpc-go.
Hi stanhu@, it difficult to find a root cause with the limited information. I have a few questions to understand the issue better:
- Did rolling back the server to gRPC Go 1.65 resolve the issue?
- What are the kind of tests are you running? What is the network setup? For example, are client and server on the same machine/k8s pod/k8s cluster?
- How much did the error rate deviate from usual? Was it a one time occurrence or was the uptick constant?
- Did you see any increase in CPU/memory usage or performance degradation of the server that could indicate it was under high load?
from grpc-go.
Also, if you can provide a way to repro the issue, investigation would become much easier.
from grpc-go.
Related Issues (20)
- encoding.GetCodec(proto.Name) broke in 1.66.0 HOT 7
- Create tests for two potential cardinality violation bugs HOT 1
- Backport #7571 to 1.66 once merged HOT 2
- Why is Metadata still being used instead of Attributes in clientconn.go? HOT 3
- Feature Request: Add Support for Generating Full Method Names List for Service-Level gRPC Interceptors
- xds: v1.66.0 regression in `xds.BootstrapContentsForTesting` HOT 11
- mem package & bufferPoolingThreshold HOT 3
- Generic Streams from protoc-gen-go-grpc are not detected by mock tools HOT 4
- Allow generated handlers to check the correct errors are returned at compile time HOT 1
- Flaky Test: xds/TestUnmarshalListener_WithUpdateValidatorFunc HOT 2
- gRPC server rarely returns UNAVAILABLE on seemingly successful requests HOT 14
- Flaky test: Test/ClientCloseReturnsEarlyWhenGoAwayWriteHangs HOT 4
- Where are the v1.66.1 release notes? HOT 3
- google.golang.org/grpc v1.66.1 is missing a retraction HOT 4
- gRPC Server Sends RST_STREAM without trailers when TCP Reassembly occurs HOT 9
- 1.66.0 - increase in produced zero addresses HOT 10
- Flaky test: TestServeAndCloseDoNotRace HOT 2
- panic: send on closed channel HOT 3
- mem.NewBuffer() should look at slice capacity? HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from grpc-go.