Allow to check whether a container was deleted #35

Closed
opened 2023-08-07 11:44:15 +00:00 by fyrchik · 2 comments
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:

  1. Container exists: cid -> <container>
  2. 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
help wanted
discussion
good first issue
P1
labels 2023-08-07 11:44:15 +00:00
Author
Owner

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

We could also save session token instead of single `[]byte{0}`
fyrchik self-assigned this 2023-08-09 07:12:04 +00:00
Author
Owner

Closed via #36

Closed via #36
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
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
No description provided.