aarifullin/frostfs-node
1
0
Fork 0
forked from TrueCloudLab/frostfs-node
Code Issues Pull requests Projects Releases Packages Wiki Activity
frostfs-node/config/example
History
Evgenii Stratonikov 351fdd9fa2 [#2246] node: Allow to configure tombsone lifetime 
Currently, DELETE service sets tombstone expiration epoch to
`current epoch + 5`. This works less than ideal in private networks
where an epoch can be e.g. 10 minutes. In this case, after a node is
unavailable for more than 1 hour, already deleted objects have a chance
to reappear.

After this commit tombstone lifetime can be configured.

Signed-off-by: Evgenii Stratonikov <e.stratonikov@yadro.com>
2023-02-20 13:53:27 +03:00
..
cli.yaml Move to frostfs-node 2022-12-28 15:04:29 +03:00
ir-control.yaml Move to frostfs-node 2022-12-28 15:04:29 +03:00
ir.env [#1] Fix viper env prefix in cli tools 2023-02-06 17:41:14 +03:00
ir.yaml [#1] Fix viper env prefix in cli tools 2023-02-06 17:41:14 +03:00
node-control.yaml Move to frostfs-node 2022-12-28 15:04:29 +03:00
node.env [#2246] node: Allow to configure tombsone lifetime 2023-02-20 13:53:27 +03:00
node.json [#2246] node: Allow to configure tombsone lifetime 2023-02-20 13:53:27 +03:00
node.yaml [#2246] node: Allow to configure tombsone lifetime 2023-02-20 13:53:27 +03:00
README.md [#1] Fix viper env prefix in cli tools 2023-02-06 17:41:14 +03:00

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
  • Inner ring
    • YAML: ir.yaml
  • CLI
    • YAML: cli.yaml

Environment variables

  • Storage node: node.env
  • Inner ring: ir.env