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
..
common.go	[#1310] object: Move target initialization to separate package	2024-09-05 13:03:58 +00:00
dispatcher.go	[#1310] object: Move target initialization to separate package	2024-09-05 13:03:58 +00:00
distributed.go	[#1431] node: Fix comment format	2024-10-15 08:53:59 +00:00
ec.go	[#1427] object: Fix Put for EC object when node unavailable	2024-10-11 16:53:30 +03:00
ec_test.go	[#1427] object: Fix Put for EC object when node unavailable	2024-10-11 16:53:30 +03:00
local.go	[#1433] services/object: Put object before auxiliary info	2024-10-17 14:43:13 +03:00
remote.go	[#1310] object: Move target initialization to separate package	2024-09-05 13:03:58 +00:00
writer.go	[#1412] engine: Add IsIndexedContainer flag	2024-10-08 11:41:49 +03:00