mirror of
https://github.com/tendermint/tendermint.git
synced 2026-09-18 22:14:35 +00:00
ci: add markdown linter (#146)
This commit is contained in:
@@ -5,14 +5,14 @@ and restoring state machine snapshots. For more information, see the [state sync
|
||||
|
||||
The state sync reactor has two main responsibilites:
|
||||
|
||||
* Serving state machine snapshots taken by the local ABCI application to new nodes joining the
|
||||
* Serving state machine snapshots taken by the local ABCI application to new nodes joining the
|
||||
network.
|
||||
|
||||
* Discovering existing snapshots and fetching snapshot chunks for an empty local application
|
||||
being bootstrapped.
|
||||
|
||||
The state sync process for bootstrapping a new node is described in detail in the section linked
|
||||
above. While technically part of the reactor (see `statesync/syncer.go` and related components),
|
||||
above. While technically part of the reactor (see `statesync/syncer.go` and related components),
|
||||
this document will only cover the P2P reactor component.
|
||||
|
||||
For details on the ABCI methods and data types, see the [ABCI documentation](../../abci/abci.md).
|
||||
@@ -26,16 +26,16 @@ available snapshots:
|
||||
type snapshotsRequestMessage struct{}
|
||||
```
|
||||
|
||||
The receiver will query the local ABCI application via `ListSnapshots`, and send a message
|
||||
The receiver will query the local ABCI application via `ListSnapshots`, and send a message
|
||||
containing snapshot metadata (limited to 4 MB) for each of the 10 most recent snapshots:
|
||||
|
||||
```go
|
||||
type snapshotsResponseMessage struct {
|
||||
Height uint64
|
||||
Format uint32
|
||||
Chunks uint32
|
||||
Hash []byte
|
||||
Metadata []byte
|
||||
Height uint64
|
||||
Format uint32
|
||||
Chunks uint32
|
||||
Hash []byte
|
||||
Metadata []byte
|
||||
}
|
||||
```
|
||||
|
||||
@@ -45,9 +45,9 @@ is accepted, the state syncer will request snapshot chunks from appropriate peer
|
||||
|
||||
```go
|
||||
type chunkRequestMessage struct {
|
||||
Height uint64
|
||||
Format uint32
|
||||
Index uint32
|
||||
Height uint64
|
||||
Format uint32
|
||||
Index uint32
|
||||
}
|
||||
```
|
||||
|
||||
@@ -56,16 +56,16 @@ and respond with it (limited to 16 MB):
|
||||
|
||||
```go
|
||||
type chunkResponseMessage struct {
|
||||
Height uint64
|
||||
Format uint32
|
||||
Index uint32
|
||||
Chunk []byte
|
||||
Missing bool
|
||||
Height uint64
|
||||
Format uint32
|
||||
Index uint32
|
||||
Chunk []byte
|
||||
Missing bool
|
||||
}
|
||||
```
|
||||
|
||||
Here, `Missing` is used to signify that the chunk was not found on the peer, since an empty
|
||||
chunk is a valid (although unlikely) response.
|
||||
chunk is a valid (although unlikely) response.
|
||||
|
||||
The returned chunk is given to the ABCI application via `ApplySnapshotChunk` until the snapshot
|
||||
is restored. If a chunk response is not returned within some time, it will be re-requested,
|
||||
@@ -73,5 +73,5 @@ possibly from a different peer.
|
||||
|
||||
The ABCI application is able to request peer bans and chunk refetching as part of the ABCI protocol.
|
||||
|
||||
If no state sync is in progress (i.e. during normal operation), any unsolicited response messages
|
||||
are discarded.
|
||||
If no state sync is in progress (i.e. during normal operation), any unsolicited response messages
|
||||
are discarded.
|
||||
|
||||
Reference in New Issue
Block a user