dstepanov-yadro
pushed to feat/OBJECT-3310 at dstepanov-yadro/frostfs-node
2023-04-12 06:37:01 +00:00
Tracing for get object
Can we create a custom attributes for this? Like zap.Stringer. When tracing is disabled it seems not worth doing this allocations.
WithAttributes
receives KeyValue
struct. `attributes.Str…
dstepanov-yadro
pushed to feat/OBJECT-3310 at dstepanov-yadro/frostfs-node
2023-04-11 15:28:55 +00:00
dstepanov-yadro
pushed to feat/OBJECT-3310 at dstepanov-yadro/frostfs-node
2023-04-11 15:22:52 +00:00
dstepanov-yadro
pushed to feat/OBJECT-3310 at dstepanov-yadro/frostfs-node
2023-04-11 15:05:26 +00:00
dstepanov-yadro
pushed to feat/OBJECT-3310 at dstepanov-yadro/frostfs-node
2023-04-11 14:03:44 +00:00
dstepanov-yadro
pushed to tracing_node at dstepanov-yadro/frostfs-dev-env
2023-04-11 13:32:02 +00:00
WIP: storage: Enable tracing
dstepanov-yadro
created branch tracing_node in dstepanov-yadro/frostfs-dev-env
2023-04-11 12:45:56 +00:00
dstepanov-yadro
pushed to tracing_node at dstepanov-yadro/frostfs-dev-env
2023-04-11 12:45:56 +00:00
Tracing for get object
@aarifullin @fyrchik contextcheck
linter violation for evacuate was fixed after review
dstepanov-yadro
pushed to feat/OBJECT-3310 at dstepanov-yadro/frostfs-node
2023-04-11 12:13:51 +00:00
dstepanov-yadro
pushed to feat/OBJECT-3310 at dstepanov-yadro/frostfs-node
2023-04-11 11:59:25 +00:00
Tracing for get object
It's about using context.Background()
for shutting down. If e use the main context of the application, then it will already be canceled at this point.
[#118] node: add unit concurrent tests for blobstor
to check the error from deletion because I check concurrent deletes
Yes, it's true. I'm talking about the fact that after deletion there should be no object exist. Maybe delete
does not…