Ekaterina Lebedeva
06be16b716
Some checks failed
Vulncheck / Vulncheck (pull_request) Successful in 3m6s
Pre-commit hooks / Pre-commit (pull_request) Successful in 3m29s
Tests and linters / gopls check (pull_request) Successful in 3m57s
Tests and linters / Tests with -race (pull_request) Failing after 5m52s
Tests and linters / Run gofumpt (pull_request) Successful in 5m59s
DCO action / DCO (pull_request) Successful in 6m15s
Tests and linters / Tests (pull_request) Failing after 6m47s
Build / Build Components (pull_request) Successful in 7m50s
Tests and linters / Staticcheck (pull_request) Successful in 7m59s
Tests and linters / Lint (pull_request) Successful in 8m40s
* Added new method for listing containers to container service. It opens stream and sends containers in batches. * Added TransportSplitter wrapper around ExecutionService to split container ID list read from contract in parts that are smaller than grpc max message size. Batch size can be changed in node configuration file (as in example config file). * Changed `container list` implementaion in cli: now ListStream is called by default. Old List is called only if ListStream is not implemented. * Changed `internalclient.ListContainersPrm`.`Account` to `OwnerID` since `client.PrmContainerList`.`Account` was renamed to `OwnerID` in sdk. Signed-off-by: Ekaterina Lebedeva <ekaterina.lebedeva@yadro.com> |
||
---|---|---|
.. | ||
cli.yaml | ||
ir-control.yaml | ||
ir.env | ||
ir.yaml | ||
node-control.yaml | ||
node.env | ||
node.json | ||
node.yaml | ||
README.md |
Examples of correct configuration file structures
Here are files in all supported formats and with all possible configuration values of FrostFS applications. See node.yaml for configuration notes.
All parameters are correct, however, they are for informational purposes only. It is not recommended transferring these configs for real application launches.
Config files
- Storage node
- JSON:
node.json
- YAML:
node.yaml
- JSON:
- Inner ring
- YAML:
ir.yaml
- YAML:
- CLI
- YAML:
cli.yaml
- YAML:
Multiple configs
You can split your configuration to several files.
For example, you can use separate yaml file for each shard or each service (pprof, prometheus).
You must use --config-dir
flag to process several configs:
$ ./bin/frotsfs-node --config ./config/example/node.yaml --config-dir ./dir/with/additional/configs
When the --config-dir
flag set, the application:
- reads all
*.y[a]ml
files from provided directory, - use Viper's MergeConfig functionality to produce the final configuration,
- files are being processing in alphanumerical order so that
01.yaml
may be extended with contents of02.yaml
, so if a field is specified in multiple files, the latest occurrence takes effect.
So if we have the following files:
# 00.yaml
logger:
level: debug
pprof:
enabled: true
address: localhost:6060
prometheus:
enabled: true
address: localhost:9090
# dir/01.yaml
logger:
level: info
pprof:
enabled: false
# dir/02.yaml
logger:
level: warn
prometheus:
address: localhost:9091
and provide the following flags:
$ ./bin/frotsfs-node --config 00.yaml --config-dir dir
result config will be:
logger:
level: warn
pprof:
enabled: false
address: localhost:6060
prometheus:
enabled: true
address: localhost:9091
Environment variables
- Storage node:
node.env
- Inner ring:
ir.env