Github url

grpc-go

by grpc

grpc /grpc-go

The Go language implementation of gRPC. HTTP/2 based RPC

11.8K Stars 2.5K Forks Last release: 19 days ago (v1.30.0) Apache License 2.0 3.4K Commits 75 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:

gRPC-Go

Build StatusGoDocGoReportCard

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.

Installation

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 google.golang.org/grpc

With Go module support (Go 1.11+), simply

import "google.golang.org/grpc"

in your source code and

go [build|run|test]

will automatically download the necessary dependencies (Go modules ref).

If you are trying to access grpc-go from within China, please see theFAQ below.

Prerequisites

gRPC-Go officially supports thethree latest major releases of Go.

Documentation

Performance

Performance benchmark data for grpc-go and other languages is maintained inthis dashboard.

Status

General Availability Google Cloud Platform Launch Stages.

FAQ

I/O Timeout Errors

The

golang.org

domain may be blocked from some countries.

go get

usually produces an error like the following when this happens:

$ go get -u google.golang.org/grpc package google.golang.org/grpc: unrecognized import path "google.golang.org/grpc" (https fetch: Get https://google.golang.org/grpc?go-get=1: dial tcp 216.239.37.1:443: i/o timeout)

To build Go code, there are several options:

  • Set up a VPN and access google.golang.org through that.

Without Go module support:

git clone

the repo manually:

git clone https://github.com/grpc/grpc-go.git $GOPATH/src/google.golang.org/grpc

You will need to do the same for all of grpc's dependencies in

golang.org

, e.g.

golang.org/x/net

.

  • With Go module support: it is possible to use the
    replace
    feature of
    go mod
    to create aliases for golang.org packages. In your project's directory:
go mod edit -replace=google.golang.org/grpc=github.com/grpc/[email protected] go mod tidy go mod vendor go build -mod=vendor

Again, this will need to be done for all transitive dependencies hosted on golang.org as well. Please refer to this issue in the golang repo regarding this concern.

Compiling error, undefined: grpc.SupportPackageIsVersion

If you are using Go modules:

Please ensure your gRPC-Go version is

require

d at the appropriate version in the same module containing the generated

.pb.go

files. For example,

SupportPackageIsVersion6

needs

v1.27.0

, so in your

go.mod

file:

module <your module name>

require (
    google.golang.org/grpc v1.27.0
)
</your>
If you are not using Go modules:

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

go get -u github.com/golang/protobuf/{proto,protoc-gen-go}
  • go get -u google.golang.org/grpc
  • 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:

GRPC\_GO\_LOG\_VERBOSITY\_LEVEL=99 GRPC\_GO\_LOG\_SEVERITY\_LEVEL=info

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 1. bytes disrupted, possibly by a proxy in between 1. server shutdown 1. Keepalive parameters caused connection shutdown, for example if you have configured your server to terminate connections regularly to trigger DNS lookups. If this is the case, you may want to increase your MaxConnectionAgeGrace, to allow longer RPC calls to finish.

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.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.