TrueCloudLab/frostfs-node
20
1
Fork 27
Code Issues 100 Pull requests 5 Projects Releases 1 Activity Actions

Fix/Allow reading expired locked object #56

Merged
carpawell merged 1 commit from fix/expired-locked-obj into master 2023-02-21 06:56:58 +00:00
Conversation 0 Commits 1 Files changed 3 +27
carpawell commented 2023-02-15 16:27:32 +00:00 (Migrated from github.com)
Copy link

Related to https://github.com/TrueCloudLab/frostfs-api/issues/2.

Related to https://github.com/TrueCloudLab/frostfs-api/issues/2.
acid-ant (Migrated from github.com) reviewed 2023-02-16 05:33:17 +00:00
fyrchik (Migrated from github.com) reviewed 2023-02-16 06:05:54 +00:00
pkg/local_object_storage/metabase/exists.go
@ -103,0 +104,4 @@
if objectLocked(tx, addr.Container(), addr.Object()) {
return 0
}
fyrchik (Migrated from github.com) commented 2023-02-16 06:05:49 +00:00
Copy link

Can we have an explicit unit-test for this behaviour?

Can we have an explicit unit-test for this behaviour?
carpawell (Migrated from github.com) reviewed 2023-02-17 14:14:37 +00:00
pkg/local_object_storage/metabase/exists.go
@ -103,0 +104,4 @@
if objectLocked(tx, addr.Container(), addr.Object()) {
return 0
}
carpawell (Migrated from github.com) commented 2023-02-17 14:14:36 +00:00
Copy link

sure, added

sure, added
acid-ant (Migrated from github.com) reviewed 2023-02-17 14:24:38 +00:00
fyrchik (Migrated from github.com) reviewed 2023-02-20 10:47:36 +00:00
pkg/local_object_storage/metabase/lock_test.go
@ -172,0 +183,4 @@
require.ErrorIs(t, err, meta.ErrObjectIsExpired)
// lock the obj
require.NoError(t, db.Lock(addr.Container(), oidtest.ID(), []oid.ID{addr.Object()}))
fyrchik (Migrated from github.com) commented 2023-02-20 10:47:33 +00:00
Copy link

Can we lock an already expired object or is it only for tests here?

Can we _lock_ an already expired object or is it only for tests here?
carpawell (Migrated from github.com) reviewed 2023-02-20 10:53:25 +00:00
pkg/local_object_storage/metabase/lock_test.go
@ -172,0 +183,4 @@
require.ErrorIs(t, err, meta.ErrObjectIsExpired)
// lock the obj
require.NoError(t, db.Lock(addr.Container(), oidtest.ID(), []oid.ID{addr.Object()}))
carpawell (Migrated from github.com) commented 2023-02-20 10:53:25 +00:00
Copy link

Can we lock an already expired object

yes, and i do not see any problems with that, you? in practice i think that is almost impossible if GC is configured to be relatively fast

> Can we lock an already expired object yes, and i do not see any problems with that, you? in practice i think that is almost impossible if GC is configured to be relatively fast
fyrchik (Migrated from github.com) reviewed 2023-02-20 12:51:53 +00:00
pkg/local_object_storage/metabase/lock_test.go
@ -172,0 +183,4 @@
require.ErrorIs(t, err, meta.ErrObjectIsExpired)
// lock the obj
require.NoError(t, db.Lock(addr.Container(), oidtest.ID(), []oid.ID{addr.Object()}))
fyrchik (Migrated from github.com) commented 2023-02-20 12:51:52 +00:00
Copy link

Unexpired object should not exits, LOCKing it postfactum seems wrong.

Unexpired object should not exits, `LOCK`ing it postfactum seems wrong.
fyrchik (Migrated from github.com) reviewed 2023-02-20 12:52:04 +00:00
pkg/local_object_storage/metabase/lock_test.go
@ -172,0 +183,4 @@
require.ErrorIs(t, err, meta.ErrObjectIsExpired)
// lock the obj
require.NoError(t, db.Lock(addr.Container(), oidtest.ID(), []oid.ID{addr.Object()}))
fyrchik (Migrated from github.com) commented 2023-02-20 12:52:03 +00:00
Copy link

Again, not for this PR.

Again, not for this PR.
fyrchik (Migrated from github.com) approved these changes 2023-02-21 06:56:51 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
fyrchik
Labels
Clear labels   
P0

Highest

  
P1

High

  
P2

Medium

  
P3

Low

  
badger

Badger DB related issues

  
frostfs-adm

   
frostfs-cli

   
frostfs-ir

   
frostfs-lens

   
frostfs-node

   
good first issue

Good for newcomers

  
triage
  
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
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
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
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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-node#56
No description provided.
Delete branch "fix/expired-locked-obj"

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?