Container policy violation in dynamic data slicing with TTL=1 #1451

Open
opened 2025-12-28 17:23:03 +00:00 by sami · 1 comment
Owner

Originally created by @cthulhu-rider on GitHub (Jul 4, 2025).

  • user requests slicing data into objects and storing them in the container by attaching session token
  • user configures request proxy by TTL field

Expected Behavior

objects are be stored according to container policy (e.g. in 3 replicas) regardless of TTL

Current Behavior

objects are just saved locally

Possible Solution

ignore TTL when slicing is requested

Steps to Reproduce (for bugs)

$ neofs-adm fschain set-config --alphabet-wallets ../devenv/services/ir1/alphabet/ -r http://ir01.neofs.devenv:30333 MaxObjectSize=1000
$ neofs-cli object put -r s01.neofs.devenv:8080 -w ../devenv/wallets/wallet.json --cid GXW6LuwSaeMSHifTY2jpaEcyLg3WPKH7CgjLasKNZ6R3 --file testfile_4k --ttl 1

Context

prepare for #3420

Regression

no

Your Environment

Originally created by @cthulhu-rider on GitHub (Jul 4, 2025). - user requests slicing data into objects and storing them in the container by attaching session token - user configures request proxy by TTL field ## Expected Behavior objects are be stored according to container policy (e.g. in 3 replicas) regardless of TTL ## Current Behavior objects are just saved locally ## Possible Solution ignore TTL when slicing is requested ## Steps to Reproduce (for bugs) ``` $ neofs-adm fschain set-config --alphabet-wallets ../devenv/services/ir1/alphabet/ -r http://ir01.neofs.devenv:30333 MaxObjectSize=1000 $ neofs-cli object put -r s01.neofs.devenv:8080 -w ../devenv/wallets/wallet.json --cid GXW6LuwSaeMSHifTY2jpaEcyLg3WPKH7CgjLasKNZ6R3 --file testfile_4k --ttl 1 ``` ## Context prepare for #3420 ## Regression no ## Your Environment * 832748964dd85ee1f6e7eb2d202380a98508e57b
Author
Owner

@roman-khimov commented on GitHub (Jul 4, 2025):

The concept of TTL as it's used in NeoFS is flawed.

@roman-khimov commented on GitHub (Jul 4, 2025): The concept of TTL as it's used in NeoFS is flawed.
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
nspcc-dev/neofs-node#1451
No description provided.