ayanamist

Upgrading itself cause issues but not new changes need to be upgraded. Let me explains: Since nearly all java applications can't be hot upgraded(keep tcp connection), the normal upgrade process...

Thanks for `server.shutdown()` will send GOAWAY, which will help to solve the first problem i mentioned. What i am asking for is > Can maxConnectionAge related settings be changed during...

The client is not under my team's control. Our team can communicate to the client team "we will have an upgrade which will make you receive some error reports for...

The ones i listed above is the real case i meet in old time: a grpc-go client which use http2 implementation in go runtime but buggy, connect to our grpc-java...

At that time, it is my server supporting. Nearly all go client using http2 have to use RoundTrip, explicit or implicit. Yes, all client need to support GOAWAY, but until...

My server is a grpc-java application provides gateway function to cross language clients including go, we maintains a grpc-java fork years ago. The cause of go side is told from...

Interesting, we are talking about a solution to avoid unexpected break but not a known issue which you constantly talk about. Anyway, you close as you like it.

Sorry but they are born much earlier than my application.

I always talks about case 1, which fixed by maintaining a fork, but not friendly when a new grpc-java user comes. The step 5 is not always working. We need...

> Right now it seems there's no reason to believe step 4 will happen. Very ridiculous point, since there is a case i have reported and fixed in my side....