metabase: Set storageID even if there is no object in metabase #1008

Merged

dstepanov-yadro merged 1 commit from dstepanov-yadro/frostfs-node:fix/flush_upgrade_storage_id into master

2024-02-28 13:53:42 +00:00

Author	SHA1	Message	Date
Dmitrii Stepanov	918613546f	[#1008 ] metabase: Do not update storageID on put All checks were successful DCO action / DCO (pull_request) Successful in 4m56s Details Build / Build Components (1.21) (pull_request) Successful in 7m52s Details Build / Build Components (1.20) (pull_request) Successful in 8m11s Details Vulncheck / Vulncheck (pull_request) Successful in 8m9s Details Tests and linters / Staticcheck (pull_request) Successful in 9m58s Details Tests and linters / Lint (pull_request) Successful in 10m42s Details Tests and linters / Tests (1.20) (pull_request) Successful in 12m14s Details Tests and linters / Tests with -race (pull_request) Successful in 12m17s Details Tests and linters / Tests (1.21) (pull_request) Successful in 12m34s Details There may be a race condition between put an object and flushing the writecache: 1. Put object to the writecache 2. Writecache flushes object to the blobstore and sets blobstore's storageID 3. Put object to the metabase, set writecache's storageID Signed-off-by: Dmitrii Stepanov <d.stepanov@yadro.com>	2024-02-28 11:01:50 +03:00