forked from TrueCloudLab/frostfs-node
Evgenii Stratonikov
351fdd9fa2
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> |
||
|---|---|---|
| .. | ||
| apiclient | ||
| contracts | ||
| control | ||
| engine | ||
| grpc | ||
| internal | ||
| logger | ||
| metrics | ||
| morph | ||
| node | ||
| object | ||
| policer | ||
| profiler | ||
| replicator | ||
| test | ||
| tree | ||
| calls.go | ||
| calls_test.go | ||
| cast.go | ||
| cast_test.go | ||
| config.go | ||
| opts.go | ||