Imporve `from` handling logic in tree service synchronization #741

New Issue

Closed

opened 2023-10-16 08:18:32 +00:00 by fyrchik · 0 comments

fyrchik commented

2023-10-16 08:18:32 +00:00

Owner

Node left the netmap.
All nodes in the container synchronize, from is increased, even though node from (1) is missing.
Node is back online and has an operation which is missing from the netmap.

Node 3 can even accept new requests with heights less then from.

One of the solutions is to store this from for each node.

1. Node left the netmap. 2. All nodes in the container synchronize, `from` is increased, even though node from (1) is missing. 3. Node is back online and has an operation which is missing from the netmap. Node 3 can even accept _new_ requests with heights less then from. One of the solutions is to store this `from` for each node.

fyrchik added the

labels 2023-10-16 08:18:38 +00:00

fyrchik added this to the v0.38.0 milestone 2023-10-16 08:18:54 +00:00

dstepanov-yadro self-assigned this 2023-11-21 09:51:05 +00:00

dstepanov-yadro referenced a pull request that will close this issue

2023-11-28 14:05:50 +00:00

Fix tree service sync #829

fyrchik closed this issue

2023-11-30 12:45:05 +00:00

fyrchik referenced this issue from a commit

2023-11-30 12:45:06 +00:00

[#741] treesvc: Remove unused height variables

fyrchik referenced this issue from a commit

2023-11-30 12:45:06 +00:00

[#741] treesvc: Do not update sync height if some node is unavailable

fyrchik referenced this issue from a commit

2023-11-30 12:45:07 +00:00

[#741] treesvc: Refactor tree sync

Sign in to join this conversation.

No Label

good first issue

No Milestone

No Assignees

1 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#741

There is no content yet.