wlf f051014ac2 提交正常运行的所有代码 1 rok pred
..
balancer f051014ac2 提交正常运行的所有代码 1 rok pred
binarylog f051014ac2 提交正常运行的所有代码 1 rok pred
codes f051014ac2 提交正常运行的所有代码 1 rok pred
connectivity f051014ac2 提交正常运行的所有代码 1 rok pred
credentials f051014ac2 提交正常运行的所有代码 1 rok pred
encoding f051014ac2 提交正常运行的所有代码 1 rok pred
grpclog f051014ac2 提交正常运行的所有代码 1 rok pred
internal f051014ac2 提交正常运行的所有代码 1 rok pred
keepalive f051014ac2 提交正常运行的所有代码 1 rok pred
metadata f051014ac2 提交正常运行的所有代码 1 rok pred
naming f051014ac2 提交正常运行的所有代码 1 rok pred
peer f051014ac2 提交正常运行的所有代码 1 rok pred
resolver f051014ac2 提交正常运行的所有代码 1 rok pred
stats f051014ac2 提交正常运行的所有代码 1 rok pred
status f051014ac2 提交正常运行的所有代码 1 rok pred
tap f051014ac2 提交正常运行的所有代码 1 rok pred
.travis.yml f051014ac2 提交正常运行的所有代码 1 rok pred
AUTHORS f051014ac2 提交正常运行的所有代码 1 rok pred
CONTRIBUTING.md f051014ac2 提交正常运行的所有代码 1 rok pred
LICENSE f051014ac2 提交正常运行的所有代码 1 rok pred
Makefile f051014ac2 提交正常运行的所有代码 1 rok pred
README.md f051014ac2 提交正常运行的所有代码 1 rok pred
backoff.go f051014ac2 提交正常运行的所有代码 1 rok pred
balancer.go f051014ac2 提交正常运行的所有代码 1 rok pred
balancer_conn_wrappers.go f051014ac2 提交正常运行的所有代码 1 rok pred
balancer_v1_wrapper.go f051014ac2 提交正常运行的所有代码 1 rok pred
call.go f051014ac2 提交正常运行的所有代码 1 rok pred
clientconn.go f051014ac2 提交正常运行的所有代码 1 rok pred
codec.go f051014ac2 提交正常运行的所有代码 1 rok pred
codegen.sh f051014ac2 提交正常运行的所有代码 1 rok pred
dialoptions.go f051014ac2 提交正常运行的所有代码 1 rok pred
doc.go f051014ac2 提交正常运行的所有代码 1 rok pred
go.mod f051014ac2 提交正常运行的所有代码 1 rok pred
go.sum f051014ac2 提交正常运行的所有代码 1 rok pred
install_gae.sh f051014ac2 提交正常运行的所有代码 1 rok pred
interceptor.go f051014ac2 提交正常运行的所有代码 1 rok pred
picker_wrapper.go f051014ac2 提交正常运行的所有代码 1 rok pred
pickfirst.go f051014ac2 提交正常运行的所有代码 1 rok pred
proxy.go f051014ac2 提交正常运行的所有代码 1 rok pred
resolver_conn_wrapper.go f051014ac2 提交正常运行的所有代码 1 rok pred
rpc_util.go f051014ac2 提交正常运行的所有代码 1 rok pred
server.go f051014ac2 提交正常运行的所有代码 1 rok pred
service_config.go f051014ac2 提交正常运行的所有代码 1 rok pred
stream.go f051014ac2 提交正常运行的所有代码 1 rok pred
trace.go f051014ac2 提交正常运行的所有代码 1 rok pred
version.go f051014ac2 提交正常运行的所有代码 1 rok pred
vet.sh f051014ac2 提交正常运行的所有代码 1 rok pred

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

Prerequisites

gRPC-Go requires Go 1.9 or later.

Constraints

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.

Documentation

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

Performance

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

Status

General Availability Google Cloud Platform Launch Stages.

FAQ

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.