Do not try to put to blobstor on full write cache #1552

New issue

Open

opened 2025-12-28 17:35:50 +00:00 by sami · 0 comments

sami commented

2025-12-28 17:35:50 +00:00

Owner

Originally created by @roman-khimov on GitHub (Dec 19, 2025).

I'm always frustrated when I'm thinking of write cache and blobstor relations. Currently we always try to put object to blobstor if putting to write cache fails.

Describe the solution you'd like

Don't do that in case write cache is full. If that's the case it's supposed to be flushing to blobstor at the maximum speed possible and additional threads pushing objects to blobstor directly can only slow it down. If it's full because it can't flush objects to blobstor trying this direct put doesn't help either.

Describe alternatives you've considered

Keep things as is. Current behavior is somewhat better for the case when write cache can't put objects to blobstor, but direct put somehow can. I don't see this happening, but who knows.

Additional context

https://github.com/nspcc-dev/neofs-node/pull/3744#discussion_r2635320251

Originally created by @roman-khimov on GitHub (Dec 19, 2025). ## Is your feature request related to a problem? Please describe. I'm always frustrated when I'm thinking of write cache and blobstor relations. Currently we always try to put object to blobstor if putting to write cache fails. ## Describe the solution you'd like Don't do that in case write cache is full. If that's the case it's supposed to be flushing to blobstor at the maximum speed possible and additional threads pushing objects to blobstor directly can only slow it down. If it's full because it can't flush objects to blobstor trying this direct put doesn't help either. ## Describe alternatives you've considered Keep things as is. Current behavior is somewhat better for the case when write cache can't put objects to blobstor, but direct put somehow can. I don't see this happening, but who knows. ## Additional context https://github.com/nspcc-dev/neofs-node/pull/3744#discussion_r2635320251