[#159] Add handle __SYSTEM__ sys attributes #159
Labels
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
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#159
Loading…
Reference in a new issue
No description provided.
Delete branch "dkirillov/frostfs-node:feature/add_frostfs_system_attribute"
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?
Related to TrueCloudLab/frostfs-http-gw#22
WIP: [#XX] Add handle __SYSTEM__ sys attributesto WIP: [#159] Add handle __SYSTEM__ sys attributesd8f5a139bc
tob198584b73
b198584b73
to567d8475e9
WIP: [#159] Add handle __SYSTEM__ sys attributesto [#159] Add handle __SYSTEM__ sys attributes@ -69,6 +70,8 @@ You need to change configuration environment variables to `FROSTFS_*` if you use
New config field `object.delete.tombstone_lifetime` allows to set tombstone lifetime
more appropriate for a specific deployment.
Use `__SYSTEM__` prefix for system attributes instead of `__NEOFS__`.
Not obvious whether
__NEOFS__
is still supported.@ -111,3 +111,3 @@
// expired previously for less than the one epoch duration
var expired bool
expired := isExpiredWithAttribute(tx, objectV2.SysAttributeExpEpoch, addr, currEpoch)
Can we do this only if the bucket does not exist? If it exists, we should not bother checking the second.
Also, we should validate in service that only 1 of the prefixes is used.
@ -60,7 +60,10 @@ func (db *DB) iterateExpired(tx *bbolt.Tx, epoch uint64, h ExpiredObjectHandler)
err := tx.ForEach(func(name []byte, b *bbolt.Bucket) error {
cidBytes := cidFromAttributeBucket(name, objectV2.SysAttributeExpEpoch)
Can we try having 1 bucket on the metabase level? I think translation could be done on an upper level.
Okay, it can make our code more complex without many benefits. Let's postpone this discussion.
567d8475e9
to841d5a8add
841d5a8add
to342e571d89