Allow to check whether a container was deleted #35

New Issue

Closed

opened 2023-08-07 11:44:15 +00:00 by fyrchik · 2 comments

fyrchik commented

2023-08-07 11:44:15 +00:00

Owner

Consider a situation where frostfs-node has connected to an outdated neo-go instance.
It see ContainerNotFound as a deleted container, when it reality the container was not yet created.

I suggest leaving some mark for deleted containers:

Container exists: cid -> <container>
Container removed: cid -> []byte{0}

This way we can be sure that the container was indeed removed.

Consider a situation where `frostfs-node` has connected to an outdated neo-go instance. It see `ContainerNotFound` as a deleted container, when it reality the container was not yet created. I suggest leaving some mark for deleted containers: 1. Container exists: `cid -> <container>` 2. Container removed: `cid -> []byte{0}` This way we can be _sure_ that the container was indeed removed.

fyrchik added the

good first issue

labels 2023-08-07 11:44:15 +00:00

fyrchik commented

2023-08-07 11:48:57 +00:00

Poster

Owner

We could also save session token instead of single []byte{0}

We could also save session token instead of single `[]byte{0}`

fyrchik referenced this issue from TrueCloudLab/frostfs-node

2023-08-07 12:32:04 +00:00

Double-check whether container is deleted #574

fyrchik self-assigned this 2023-08-09 07:12:04 +00:00

fyrchik referenced a pull request that will close this issue

2023-08-10 17:15:12 +00:00

contract: Add DeletionInfo() method #36

fyrchik closed this issue

2023-08-10 17:15:15 +00:00

fyrchik commented

2023-08-10 17:15:26 +00:00

Poster

Owner

Closed via #36

Closed via #36

Sign in to join this conversation.

No Label

good first issue

No Milestone

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: TrueCloudLab/frostfs-contract#35

There is no content yet.