tree: 04cafd935ec6ab2a48d9295f19504a6afa1e3f67 [path history] [tgz]
  1. .travis.yml
  2. AUTHORS
  3. CODE-OF-CONDUCT.md
  4. CONTRIBUTING.md
  5. GOVERNANCE.md
  6. LICENSE
  7. MAINTAINERS.md
  8. Makefile
  9. README.md
  10. backoff.go
  11. balancer.go
  12. balancer/
  13. balancer_conn_wrappers.go
  14. balancer_v1_wrapper.go
  15. binarylog/
  16. call.go
  17. clientconn.go
  18. codec.go
  19. codegen.sh
  20. codes/
  21. connectivity/
  22. credentials/
  23. dialoptions.go
  24. doc.go
  25. encoding/
  26. go.mod
  27. go.sum
  28. grpclog/
  29. install_gae.sh
  30. interceptor.go
  31. internal/
  32. keepalive/
  33. metadata/
  34. naming/
  35. peer/
  36. picker_wrapper.go
  37. pickfirst.go
  38. preloader.go
  39. proxy.go
  40. reflection/
  41. resolver/
  42. resolver_conn_wrapper.go
  43. rpc_util.go
  44. server.go
  45. service_config.go
  46. serviceconfig/
  47. stats/
  48. status/
  49. stream.go
  50. tap/
  51. trace.go
  52. version.go
  53. vet.sh
vendor/google.golang.org/grpc/README.md

gRPC-Go

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.

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 the FAQ below.

Prerequisites

gRPC-Go requires Go 1.9 or later.

Documentation

Performance

Performance benchmark data for grpc-go and other languages is maintained in this 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/grpc-go@latest
    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

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
  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.