TrueCloudLab/frostfs-api
26
0
Fork 17
Code Issues 11 Pull requests 1 Releases Activity Actions

Copies numbers for object delete operation #34

New issue
Open
opened 2023-08-31 15:19:58 +00:00 by alexvanin · 1 comment
alexvanin commented 2023-08-31 15:19:58 +00:00
Owner
Copy link

Is your feature request related to a problem? Please describe.

The problem is described in TrueCloudLab/frostfs-node#594
In short: when storage policy cannot be satisfied (REP 4 and one node in maintenance mode), delete operation will always fail.

Describe the solution you'd like

Delete operation produces tombstone object and puts it in nodes. Client can control number of acks from nodes with copies_number parameter of object put request. The same way it is possible to adopt copies_number or ack_number in the delete request with separate field or known x-header.

Describe alternatives you've considered

Return partial success status as it proposed in #33

## Is your feature request related to a problem? Please describe. The problem is described in https://git.frostfs.info/TrueCloudLab/frostfs-node/issues/594 In short: when storage policy cannot be satisfied (`REP 4` and one node in maintenance mode), delete operation will always fail. ## Describe the solution you'd like Delete operation produces tombstone object and puts it in nodes. Client can control number of acks from nodes with `copies_number` parameter of object put request. The same way it is possible to adopt `copies_number` or `ack_number` in the delete request with separate field or known x-header. ## Describe alternatives you've considered Return partial success status as it proposed in https://git.frostfs.info/TrueCloudLab/frostfs-api/issues/33
alexvanin added the
triage
 label 2023-08-31 15:19:58 +00:00
fyrchik commented 2023-08-31 17:05:26 +00:00
Owner
Copy link

The notion of "tombstone" already leaks outside, so I would rather use the exact same parameter name.

The notion of "tombstone" already leaks outside, so I would rather use the exact same parameter name.
realloc added this to the v2.15 - Karpinsky Ice Cap milestone 2023-09-02 15:42:57 +00:00
realloc modified the milestone from v2.15 - Karpinsky Ice Cap to v2.17 - Zemu Glacier 2023-09-04 10:41:13 +00:00
realloc added
enhancement
help wanted
good first issue
 and removed
triage
 labels 2023-09-04 10:42:42 +00:00
fyrchik was assigned by realloc 2023-09-04 10:42:54 +00:00
alexvanin was assigned by realloc 2023-09-04 10:42:54 +00:00
alexvanin was unassigned by realloc 2023-09-04 10:43:03 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
feature/compatibility
rebranding
No results found.
Labels
Clear labels   
P0

Highest

  
P1

High

  
P2

Medium

  
P3

Low

  
good first issue

Good for newcomers

  
triage

Needs to be triaged

  
Infrastructure

Infrastructure, Automation, CI/CD or DevOps related stuff

  
blocked

The issue or PR is blocked by something

  
bug

Something is not working

  
config

Configuration format update or breaking change

  
discussion

Talking about something in order to reach a decision or to exchange ideas

  
documentation

Documentation related

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
go

Language features adoption

  
help wanted

Extra attention is needed

  
internal

   
invalid

Something is wrong

  
kludge

This is a kludge and we know it

  
observability

Related to metrics, tracing and logs

  
perfomance

Perfomance related

  
question

More information is needed

  
refactoring

Refactoring

  
wontfix

This won't be fixed

No labels
P0
P1
P2
P3
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
Milestone
Clear milestone
No items
No milestone
v2.17 - Zemu Glacier
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
fyrchik
2 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-api#34
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?