Clone this repo:
  1. 22c2121 benchmark: exit after printing help when using `-h` (#2701) by yangdihangN · 13 hours ago master
  2. 66cd524 transport: stop using http.CloseNotifier in handler server (#2697) by Menghan Li · 35 hours ago
  3. d021e89 internal: fix Dial_OneBackoffPerRetryGroup (#2689) by Jean de Klerk · 36 hours ago
  4. 495133b internal: fix pickoptions in balancer_test (#2698) by Menghan Li · 2 days ago
  5. ce45558 balancer: make sure non-nil done returned by Pick is called (#2688) by Menghan Li · 3 days ago


Build Status GoDoc GoReportCard

The Go implementation of gRPC: A high performance, open source, general RPC framework that puts mobile and HTTP/2 first. For more information see the gRPC Quick Start: Go guide.


To install this package, you need to install Go and setup your Go workspace on your computer. The simplest way to install the library is to run:

$ go get -u


gRPC-Go requires Go 1.9 or later.


The grpc package should only depend on standard Go packages and a small number of exceptions. If your contribution introduces new dependencies which are NOT in the list, you need a discussion with gRPC-Go authors and consultants.


See API documentation for package and API descriptions and find examples in the examples directory.


See the current benchmarks for some of the languages supported in this dashboard.


General Availability Google Cloud Platform Launch Stages.


Compiling error, undefined: grpc.SupportPackageIsVersion

Please update proto package, gRPC package and rebuild the proto files:

  • go get -u{proto,protoc-gen-go}
  • go get -u
  • protoc --go_out=plugins=grpc:. *.proto

How to turn on logging

The default logger is controlled by the environment variables. Turn everything on by setting:


The RPC failed with error "code = Unavailable desc = transport is closing"

This error means the connection the RPC is using was closed, and there are many possible reasons, including:

  1. mis-configured transport credentials, connection failed on handshaking
  2. bytes disrupted, possibly by a proxy in between
  3. server shutdown

It can be tricky to debug this because the error happens on the client side but the root cause of the connection being closed is on the server side. Turn on logging on both client and server, and see if there are any transport errors.