raft-grpc-example - GitLite

KO | EN

gitlite — search

#dotnet #web #postgresql #cross-platform #android #redis #awesome #svg #video #json

raft-grpc-example

(★ 231)

Example code for how to get hashicorp/raft running with gRPC

파일 탐색기

ZIP 다운로드

- - .gitignore
  - hammer.go
- Makefile
- service.pb.go
- service.proto
.gitignore
application.go
go.mod
go.sum
LICENSE
main.go
README.md

# CDN으로 사용하기

jsDelivr

jsDelivr는 공개 GitHub 리포지토리를 별도 설정 없이 CDN으로 즉시 서빙합니다. 버전과 파일을 고르면 웹페이지에 바로 붙일 수 있는 링크와 예시 코드가 만들어집니다.

버전

파일

링크

예시

명령어 용어집

이 문서에서 사용된 명령어를 모아봤습니다. 낯선 명령어가 있다면 펼쳐서 확인해보세요.

🔍

`go install`

설명 보기 ▼

Compile and install packages named by the import paths.

go install

Compile and install the current package:

go install {{path/to/package}}

Compile and install a specific local package:

go install {{golang.org/x/tools/gopls}}@{{latest}}

Install the latest version of a program, ignoring `go.mod` in the current directory:

🔍

`go run`

설명 보기 ▼

Compile and run Go code without saving a binary.

go run {{path/to/file.go}}

Run a Go file:

go run {{path/to/package}}

Run a main Go package:

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

This is some example code for how to use [Hashicorp's Raft implementation](https://github.com/hashicorp/raft) with gRPC.

## Start your own cluster

```shell
$ mkdir /tmp/my-raft-cluster
$ mkdir /tmp/my-raft-cluster/node{A,B,C}
$ ./raft-grpc-example --raft_bootstrap --raft_id=nodeA --address=localhost:50051 --raft_data_dir /tmp/my-raft-cluster
$ ./raft-grpc-example --raft_id=nodeB --address=localhost:50052 --raft_data_dir /tmp/my-raft-cluster
$ ./raft-grpc-example --raft_id=nodeC --address=localhost:50053 --raft_data_dir /tmp/my-raft-cluster
$ go install github.com/Jille/raftadmin/cmd/raftadmin@latest
$ raftadmin localhost:50051 add_voter nodeB localhost:50052 0
$ raftadmin --leader multi:///localhost:50051,localhost:50052 add_voter nodeC localhost:50053 0
$ go run cmd/hammer/hammer.go &
$ raftadmin --leader multi:///localhost:50051,localhost:50052,localhost:50053 leadership_transfer
$ wait
```

You start up three nodes, and bootstrap one of them. Then you tell the bootstrapped node where to find peers. Those peers sync up to the state of the bootstrapped node and become members of the cluster. Once your cluster is running, you never need to pass `--raft_bootstrap` again.

[raftadmin](https://github.com/Jille/raftadmin) is used to communicate with the cluster and add the other nodes.

This example uses [Jille/raft-grpc-transport](https://github.com/Jille/raft-grpc-transport) to communicate between nodes using gRPC.

This example uses [Jille/raft-grpc-leader-rpc](https://github.com/Jille/raft-grpc-leader-rpc) to send RPCs to the leader.

Hammer is a client that connects to your raft cluster and sends a bunch of requests. Trigger some leadership failovers to show that it's unaffected.

## What's what

Raft uses logs to synchronize changes. Every change submitted to a Raft cluster is a log entry, which gets stored and replicated to the followers in the cluster. In this example, we use [raft-boltdb](https://github.com/hashicorp/raft-boltdb) to store these logs.
Once in a while Raft decides the logs have grown too large, and makes a snapshot. Your code is asked to write out its state. That state captures all previous logs. Now Raft can delete all the old logs and just use the snapshot. These snapshots are stored using the FileSnapshotStore, which means they'll just be files in your disk.
Raft also needs a way to talk to other nodes, that's called a Transport. This example uses [Jille/raft-grpc-transport](https://github.com/Jille/raft-grpc-transport) to communicate between nodes using gRPC.

You can see all this happening in `NewRaft()` in `main.go`.

## Your application

See `application.go`. You'll need to implement a `raft.FSM`, and you probably want a gRPC RPC interface.