Describe tombstone expiration time #7

New issue

Closed

opened 2023-02-03 11:02:21 +00:00 by ir0nbee · 2 comments

ir0nbee commented

2023-02-03 11:02:21 +00:00

(Migrated from github.com)

Let's add tombstone expiration timer to netinfo or other suitable place so that we could check its current value.
Right now it is set as a constant in the code
2540598779/cmd/frostfs-node/object.go (L319)

Let's add tombstone expiration timer to netinfo or other suitable place so that we could check its current value. Right now it is set as a constant in the code https://github.com/TrueCloudLab/frostfs-node/blob/25405987791151aea05be90a5b1ec13cdec3947f/cmd/frostfs-node/object.go#L319

fyrchik commented

2023-02-09 12:20:46 +00:00

(Migrated from github.com)

We will set it in the node configuration. From the protocol POV it is not a network value -- a user can create a tombstone themselves with any expiration epoch. This setting is for DELETE RPC where a node chooses tombstone's lifetime.
If we need to get it in runtime, we can get a tombstone object and check it's expiration epoch.

We will set it in the node configuration. From the protocol POV it is not a network value -- a user can create a tombstone themselves with _any_ expiration epoch. This setting is for DELETE RPC where a node chooses tombstone's lifetime. If we need to get it in runtime, we can get a tombstone object and check it's expiration epoch.

realloc commented

2023-03-23 13:58:40 +00:00

Owner

Now it may be set in node config in object→delete→tombstone_lifetime.

Let's close this issue.

Now it may be set in node config in [object→delete→tombstone_lifetime](https://git.frostfs.info/TrueCloudLab/frostfs-node/src/branch/master/config/example/node.yaml#L111). Let's close this issue.