-
Notifications
You must be signed in to change notification settings - Fork 79
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
services: add new service for fetching blocks from NeoFS
Close #3496 Co-authored-by: Anna Shaleva <[email protected]> Signed-off-by: Ekaterina Pavlova <[email protected]>
- Loading branch information
1 parent
d21c8f7
commit e035502
Showing
11 changed files
with
749 additions
and
48 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,88 @@ | ||
# NeoFS BlockFetcher | ||
This service was proposed as part [ Using NeoFS to store blocks and snapshots #3463](https://github.com/neo-project/neo/issues/3463). | ||
|
||
The NeoFS BlockFetcher service is designed to fetch blocks from NeoFS storage | ||
nodes and supply them to the NeoGo node. It serves as an alternative method to | ||
retrieve blocks, primarily used at the start of a node's lifecycle, providing | ||
an alternative to downloading blocks through the P2P NeoGo network. By default, | ||
the service is disabled. | ||
|
||
The NeoFS BlockFetcher service has two modes of operation: | ||
- Index File Search: Search for index files, which contain OIDs of blocks, | ||
and fetch blocks from NeoFS by provided OIDs from file. | ||
- Direct Block Search: Search and fetch blocks directly from NeoFS container. | ||
|
||
### Storage schema | ||
One container is used to store blocks and index files. Each block is stored | ||
as a separate object with a unique OID and attribute with `block.Index`. | ||
Index files contain OIDs of ordered blocks. Each index file is an object | ||
containing a specified number (`blockfetcher.indexFileSize`) of OIDs in | ||
binary form, with attributes numbered sequentially from 1 to n, where | ||
the numbers represent the continuous chain of blocks. | ||
|
||
Attributes have the following structure: `AttributeName:IntValue`. | ||
In the container are stored blocks with attributes `BlockAttribute:1`, | ||
`BlockAttribute:2`, etc. | ||
And index files with attributes `OidAttribute:1`, `OidAttribute:2`, etc. | ||
|
||
### BlockFetcher workflows | ||
1. **OID Fetching**: | ||
Depending on the mode, the service either: | ||
- Searches for index files by attribute and reads blocks OIDs from it. | ||
- Searches batches of blocks directly by attributes. | ||
|
||
OIDs are buffered (size configurable) to ensure blocks can be downloaded | ||
efficiently without delays. | ||
2. **Parallel Block Downloading**: | ||
Multiple workers (configurable) download blocks by OIDs from NeoFS in | ||
parallel. Downloaded blocks are placed into a buffer for further processing. | ||
3. **Block Insertion**: | ||
Downloaded blocks are inserted into the blockchain. The gap between blocks | ||
must remain within the block queue capacity (configurable) to ensure proper | ||
sequencing. | ||
|
||
Once all blocks in the NeoFS container are processed, the service shuts | ||
down automatically. | ||
|
||
### NeoFS BlockFetcher Configuration | ||
`NeoFSBlockFetcher` configuration section contains settings for NeoFS | ||
BlockFetcher module and has the following structure: | ||
``` | ||
NeoFSBlockFetcher: | ||
Enabled: true | ||
UnlockWallet: | ||
Path: "./wallet.json" | ||
Password: "pass" | ||
Addresses: | ||
- st1.storage.fs.neo.org:8080 | ||
Timeout: 10m | ||
DownloaderWorkersCount: 500 | ||
OIDBatchSize: 8000 | ||
BQueueSize: 16000 | ||
SkipIndexFilesSearch: false | ||
ContainerID: "EPGuD26wYgQJbmDdVBoYoNZiMKHwFMJT3A5WqPjdUHxH" | ||
BlockAttribute: "block" | ||
OidAttribute: "oid" | ||
``` | ||
where: | ||
- `Enabled` enables NeoFS BlockFetcher module. | ||
- `UnlockWallet` contains wallet settings, see | ||
[Unlock Wallet Configuration](https://github.com/nspcc-dev/neo-go/blob/master/docs/node-configuration.md#unlock-wallet-configuration) | ||
section contains wallet settings to retrieve account to sign requests to | ||
NeoFS. Without this setting, the module will use new generated private key. | ||
- `Addresses` is a list of NeoFS storage nodes addresses. | ||
- `Timeout` is a timeout for a single request to NeoFS storage node. | ||
- `ContainerID` is a container ID to fetch blocks from. | ||
- `BlockAttribute` is an attribute name of NeoFS object that contains block | ||
data. | ||
- `OidAttribute` is an attribute name of NeoFS object that contains OIDs of | ||
blocks objects. | ||
- `DownloaderWorkersCount` is a number of workers that download blocks from | ||
NeoFS. | ||
- `OIDBatchSize` is a number of OIDs to search in one request in case of | ||
SkipIndexFilesSearch=true. And is a buffer size for OIDs in both modes. | ||
- `BQueueSize` is a size of the block queue. It must be larger than | ||
`OIDBatchSize` and highly recommended to be 2*`OIDBatchSize` or 3*`OIDBatchSize`. | ||
- `SkipIndexFilesSearch` is a flag that allows skipping index files search | ||
in NeoFS storage nodes and search for blocks directly. It is set to `false` | ||
by default. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,45 @@ | ||
package config | ||
|
||
import ( | ||
"errors" | ||
"fmt" | ||
"time" | ||
|
||
cid "github.com/nspcc-dev/neofs-sdk-go/container/id" | ||
) | ||
|
||
// NeoFSBlockFetcher represents the configuration for the NeoFS block fetcher service. | ||
type NeoFSBlockFetcher struct { | ||
InternalService `yaml:",inline"` | ||
Timeout time.Duration `yaml:"Timeout"` | ||
ContainerID string `yaml:"ContainerID"` | ||
Addresses []string `yaml:"Addresses"` | ||
OIDBatchSize int `yaml:"OIDBatchSize"` // valid only for SkipIndexFilesSearch = true | ||
BlockAttribute string `yaml:"BlockAttribute"` | ||
OidAttribute string `yaml:"OidAttribute"` | ||
HeaderAttribute string `yaml:"HeaderAttribute"` | ||
DownloaderWorkersCount int `yaml:"DownloaderWorkersCount"` | ||
BQueueSize int `yaml:"BQueueSize"` | ||
SkipIndexFilesSearch bool `yaml:"SkipIndexFilesSearch"` | ||
} | ||
|
||
// Validate checks NeoFSBlockFetcher for internal consistency and ensures | ||
// that all required fields are properly set. It returns an error if the | ||
// configuration is invalid or if the ContainerID cannot be properly decoded. | ||
func (cfg *NeoFSBlockFetcher) Validate() error { | ||
if !cfg.Enabled { | ||
return nil | ||
} | ||
if cfg.ContainerID == "" { | ||
return errors.New("container ID is not set") | ||
} | ||
var containerID cid.ID | ||
err := containerID.DecodeString(cfg.ContainerID) | ||
if err != nil { | ||
return fmt.Errorf("invalid container ID: %w", err) | ||
} | ||
if cfg.BQueueSize < cfg.OIDBatchSize { | ||
return fmt.Errorf("BQueueSize (%d) is lower than OIDBatchSize (%d)", cfg.BQueueSize, cfg.OIDBatchSize) | ||
} | ||
return nil | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.