Clone this repo:
  1. ec9c18c internal: split StateRecordingBalancer in test to balancer and builder (#2578) by Menghan Li · 32 hours ago master
  2. 9f93218 cleanup: update staticcheck to version supporting modules and new checkers (#2583) by Doug Fawley · 2 days ago
  3. d7e8e3d cleanup: remove staticcheck exception (#2582) by Doug Fawley · 2 days ago
  4. 9572bbe cleanup: remove unused symbols (#2581) by Doug Fawley · 2 days ago
  5. efaac52 roundrobin: randomize starting address when rebuilding the picker (#2579) by Doug Fawley · 2 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.