Fix data race on morph component init #1444

Merged
fyrchik merged 1 commit from dstepanov-yadro/frostfs-node:fix/resync_fail_morph_client into master 2024-10-23 10:25:35 +00:00

It could be called for every shard on metabase resync concurrently and
it is possible to get state with initialized client but not initialized
contract hashes.

It could be called for every shard on metabase resync concurrently and it is possible to get state with initialized client but not initialized contract hashes.
dstepanov-yadro force-pushed fix/resync_fail_morph_client from 1ff7d9fb6a to e515dd4582 2024-10-23 07:42:04 +00:00 Compare
dstepanov-yadro requested review from storage-core-committers 2024-10-23 07:46:55 +00:00
dstepanov-yadro requested review from storage-core-developers 2024-10-23 07:46:56 +00:00
Owner

Why do we go to the network on resync?

Why do we go to the network on resync?
Author
Member

Why do we go to the network on resync?

To get container properties (indexed or not)

> Why do we go to the network on resync? To get container properties (indexed or not)
acid-ant approved these changes 2024-10-23 09:33:49 +00:00
aarifullin approved these changes 2024-10-23 09:50:40 +00:00
aarifullin left a comment
Member

Good!

Good!
fyrchik merged commit e515dd4582 into master 2024-10-23 10:25:35 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: TrueCloudLab/frostfs-node#1444
No description provided.