Evgenii Stratonikov b42bcdc6fa [#1433] services/object: Put object before auxiliary info ... Consider the following operations ordering: 1. Inhume(with tombstone A) --> add tombstone mark for an object 2. --> new epoch arives 3. --> GCMark is added for a tombstone A, because it is unavailable 4. Put(A) --> return error, because the object already has a GCMark It is possible, and I have successfully reproduced it with a test on the shard level. However, the error is related to the specific _ordering_ of operations with engine. And triggering race-conditions like this is only possible on a shard level currently, so no tests are written. Signed-off-by: Evgenii Stratonikov <e.stratonikov@yadro.com>		2024-10-17 14:43:13 +03:00
..
ape	[#1388] apeSvc: Drop unused and make annotations	2024-09-25 08:55:38 +00:00
core	[#1431] node: Fix comment format	2024-10-15 08:53:59 +00:00
innerring	[#1431] node: Fix 'empty slice declaration using a literal'	2024-10-15 08:53:59 +00:00
local_object_storage	[#1433] shard/test: Use WithDisabledGC() option where possible	2024-10-17 14:38:07 +03:00
morph	[#1431] node: Fix 'empty slice declaration using a literal'	2024-10-15 08:53:59 +00:00
network	[#1342] network/cache: Add node address to error multiClient	2024-10-15 14:05:33 +00:00
services	[#1433] services/object: Put object before auxiliary info	2024-10-17 14:43:13 +03:00
tracing	[#146] node: Add trace_id to logs	2023-09-27 11:05:27 +03:00
util	[#1431] node: Fix comment format	2024-10-15 08:53:59 +00:00